[00:13] <TheMuso> ./c
[07:02] <jibel> good morning
[07:03] <didrocks> salut jibel, ça va?
[07:03] <jibel> salut didrocks! ça va et toi ?
[07:03] <didrocks> ça va bien :)
[10:26] <xnox> didrocks: is lp:bamf actually in the auto-landing mode atm? I have FTBFS fix to upload and I'm not sure if I should do a direct upload + MP or just a MP?
[10:27] <didrocks> xnox: it's in auto-landing mode
[10:27] <didrocks> xnox: you did fix the test due to new glib?
[10:27] <didrocks> xnox: Trevinho was working on it AFAIK
[10:28] <xnox> .... i was more about ftbfs due to new gir....
[10:28] <xnox> https://launchpadlibrarian.net/135635599/buildlog_ubuntu-raring-i386.bamf_0.4.0daily13.03.07-0ubuntu1_FAILEDTOBUILD.txt.gz
[10:28] <Trevinho> didrocks: I fixed the tests,,,
[10:28] <didrocks> Trevinho: ah nice, I didn't spot it in trunk :)
[10:28] <didrocks> Trevinho: did you see my and cyphermox's ping?
[10:29] <didrocks> Trevinho: about the missing changelog entry, he didn't want to manually publish yesterday because of that
[10:29] <Trevinho> didrocks: I saw the cyphermox one... I thought I had linked the bug actually
[10:29] <didrocks> Trevinho: linking is too late once merged
[10:29] <didrocks> Trevinho: you need to add a changelog entry then
[10:29] <didrocks> cyphermox: ^
[10:30] <didrocks> this is clear in the daily release FAQ though :/
[10:30] <Trevinho> didrocks: was it related to https://code.launchpad.net/~3v1n0/bamf/fix-trunk-compilation-tests/+merge/156049 ? since the other ones have a bugs
[10:31] <didrocks> Trevinho: yes
[10:31] <Trevinho> didrocks: ah, I didn't open a bug for that, sorry :/
[10:31] <Trevinho> didrocks: I didn't think it was needed
[10:31] <didrocks> Trevinho: seems cyphermox wants a mention in the changelog at least
[10:31] <didrocks> as you changed something in the packaging
[10:31] <Trevinho> didrocks: ah, right... I was thinking to that as well
[10:32] <didrocks> Trevinho: can you please do that?
[10:32] <Trevinho> didrocks: ok, need a new branch or direct push?
[10:32] <didrocks> Trevinho: direct push is fine by me
[10:32] <Trevinho> didrocks: ok
[10:32] <didrocks> then cyphermox can rebuild I guess bamf
[10:32] <didrocks> and manually publish it today
[10:33] <Trevinho> didrocks: however.... that sounds weird since I had a bug for https://code.launchpad.net/~3v1n0/bamf/class-to-index-file that actually was the one that changed the debian code (https://bugs.launchpad.net/bamf/+bug/1161430)
[10:33] <ubot2`> Launchpad bug 1161430 in bamf "Bamf index file is not used to store the .desktop class name or the OnlyShowIn parameters" [Medium,New]
[10:33] <Trevinho> didrocks: that's why I didn't change the changelog manually
[10:33] <Trevinho> didrocks: I thought about doing it, but since I had a bug I just linked to it to make your bots to write it
[10:33] <didrocks> Trevinho: this bug is in
[10:33] <Trevinho> didrocks: ah, ok
[10:34] <didrocks> Trevinho: is it linked to that packaging change? I don't see the link with the gir thing
[10:34] <Trevinho> didrocks: I didn't change anything gir-related in the last days... I only changed the indexer
[10:35] <Trevinho> didrocks: the gir was something older that had a changelong
[10:35] <Trevinho> changelog*
[10:35] <didrocks> Trevinho: can you check with him?
[10:35] <Trevinho> 0.4.0daily12.12.05-0ubuntu2
[10:35] <didrocks> will be quicker
[10:35] <Trevinho> didrocks: ok
[10:35] <didrocks> than having me being the man in the middle :)
[10:36] <Trevinho> didrocks: you're always the man in the middle... Our security hole! :D
[10:36] <didrocks> :p
[10:36] <Trevinho> didrocks: just one thing about changelog... Should I edit the last revision, or adding a new one?
[10:37] <didrocks> Trevinho: if the last changing is UNRELEASED, just add an entry to it
[10:37] <didrocks> Trevinho: if it's a released one (raring… so on) dch -i and then add an entry
[10:38] <Trevinho> didrocks: it seems relased: bamf (0.4.0daily13.03.07-0ubuntu1) raring; urgency=low
[10:38] <Trevinho> Automatic snapshot from revision 523
[10:38] <didrocks> Trevinho: yep
[10:43] <didrocks> Trevinho: https://wiki.ubuntu.com/DailyRelease/FAQ#I_have_a_big_change_that_needs_to_be_mention_in_debian.2BAC8-changelog.2C_but_not_bug_for_it_.28or_I_didn.27t_link_to_a_bug_before_merging FYI
[10:43] <didrocks> (just wrote it)
[10:44] <Trevinho> didrocks: nice, however in my case I did linked it before merging, but that's another story :)
[10:45] <Trevinho> didrocks: http://bazaar.launchpad.net/~unity-team/bamf/trunk/revision/528
[10:47] <didrocks> Trevinho: hum?
[10:47] <didrocks> Trevinho: no, that one is not needed
[10:47] <Trevinho> didrocks: I've just added it, is it fine?
[10:47] <didrocks> Trevinho: for the linked one
[10:47] <didrocks> Trevinho: I guess cyphermox was complaining about   * libbamf: use scanner-flags for introspection, fixes a compilation error.
[10:47] <didrocks> this one was not linked to a bug
[10:47] <didrocks> the others are not needed
[10:48] <Trevinho> mh, misunderstanding then -_-
[10:48] <didrocks> Trevinho: see https://jenkins.qa.ubuntu.com/view/cu2d/view/Raring/view/Indicators/job/cu2d-indicators-raring-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_bamf_0.4.0daily13.04.02-0ubuntu1.diff
[10:49] <Trevinho> didrocks: ah, I was not seeing them in trunk...
[10:49] <Trevinho> didrocks: so I just add the libbamf compilation fix to the changelog..
[10:50] <didrocks> Trevinho: sounds good :)
[10:51] <Trevinho> didrocks: I keep the debian/bamfdaemon.postinst line though, so that it can be more clear what it changes packaging side...
[10:54] <xnox> you can reject https://code.launchpad.net/~xnox/bamf/fix-ftbfs/+merge/156514 it's not needed.
[10:54] <xnox> fixed in trunk already.
[11:00] <GunnarHj> seb128: Hi Seb, can you please take a look at bug 1163142? Think it is an aptdaemon thing, but I'm anything but sure.
[11:00] <ubot2`> GunnarHj: Error: Could not gather data from Launchpad for bug #1163142 (https://launchpad.net/bugs/1163142). The error has been logged
[11:01] <seb128> GunnarHj, try maybe asking cjwatson on #ubuntu-devel, that seems like a dpkg (or debconf) issue
[11:02] <GunnarHj> seb128: Ok, I'll try that.
[13:06] <Sweetshark> seb128: ping?
[13:11] <seb128> Sweetshark, hey
[13:11] <seb128> sorry, compiz fail, had to close xchat and restart it to be able to focus it
[13:13] <ogra_> use Mir !
[13:18] <xclaesse> hm, gnome3 ppa does not have eds 3.8 neither... anyone planning to push it there? :-)
[13:19] <xclaesse> ah, it is in gnome3-staging
[13:19] <seb128> xclaesse, I guess it's a bit tricky since it breaks api/abi and will break softwares using e-d-s
[13:21] <xclaesse> seb128, ah... :/
[13:22] <xclaesse> maybe I should just stick to 3.6 API in my app then
[13:22] <seb128> xclaesse, well, I didn't check what libs changed
[13:50] <seb128> desrt, hey
[13:51] <seb128> desrt, did you see glib's gdbus-close-pending test fail like on https://launchpadlibrarian.net/135923939/buildlog_ubuntu-raring-armhf.glib2.0_2.36.0-1ubuntu1_FAILEDTOBUILD.txt.gz before?
[13:51] <seb128> g_main_context_wakeup: assertion `g_atomic_int_get (&context->ref_count) > 0' failed
[13:52] <desrt> god do i ever hate that test
[13:52] <desrt> no.  i didn't see that.
[13:52] <desrt> only on arm?
[13:53] <seb128> yes
[13:53] <seb128> doko is doing a test rebuild on the archive
[13:53] <desrt> well awesome
[13:53] <seb128> he hit that one, twice now
[13:53] <seb128> he did a retry and still get it
[13:53] <desrt> i wonder if our atomic ops are somehow not up to snuff on arm
[13:53] <desrt> huh.  reliable is nice.
[13:53] <desrt> i wonder if i could reproduce it locally on my rasp-pi or something
[13:54] <desrt> only started recently, i guess?
[13:54] <seb128> desrt, seems so
[13:54] <desrt> that's weird
[13:54] <seb128> or the ppa builders are different from the archive ones
[13:54] <seb128> which is possible
[13:54] <desrt> i was poking around in that testcase the other day because i had caused a bug
[13:54] <seb128> like virtual builds
[13:54] <desrt> but it was on a branch that i didn't merge yet
[13:54] <desrt> ah... tricky.
[13:55] <desrt> is this the first archive build you've done?
[13:55] <desrt> iirc we've had 2.35.x releases in the distro for a while, no?
[13:57] <seb128> it's like the second one
[13:57] <seb128> but we didn't have the new glib at the time of the first rebuild
[13:57] <seb128> but rebuilds are not different from ppas
[13:58] <desrt> i'm confused.
[13:58] <desrt> what is the last passing version that we had building on the same system?
[13:58] <desrt> and what is the system that produces the failure?  real hardware?
[13:59] <seb128> 2.34 was the last one
[14:00] <desrt> that doesn't make sense...
[14:00] <seb128> we don't get a lot of arm builds on ppas
[14:00] <desrt> OH
[14:00] <desrt> this is a paa?
[14:00] <desrt> *ppa
[14:00] <seb128> yes
[14:00] <desrt> so this is virt?
[14:00] <seb128> yes
[14:00] <desrt> ok
[14:00] <desrt> so probably i should not try using my rasp-pi to reproduce :)
[14:00] <seb128> feel free to say that it's a doko or #is bug :p
[14:01] <desrt> well
[14:01] <desrt> i'd like to know more :)
[14:01] <desrt> who do i query about those builders?  #is?
[14:02] <seb128> desrt, /j #ubuntu-devel to start
[14:02] <seb128> I'm asking doko there
[15:28] <didrocks> Sweetshark, qengho, jasoncwarner, mlankhorst, cyphermox, mterry, robru, desrt, tkamppeter, attente: meeting time in 2 minutes!
[15:28] <qengho> Europeans, welcome to summer time.
[15:28] <mlankhorst> :(
[15:28] <seb128> didrocks, thanks
[15:29] <seb128> (I'm around but in a call)
[15:29] <didrocks> seb128: continue slacking off, I'll cover you :)
[15:29] <didrocks> shhh, I hope jasoncwarner_ doesn't listen :p
[15:29] <seb128> roooh
[15:30] <didrocks> Sweetshark, qengho, jasoncwarner, mlankhorst, cyphermox, mterry, robru, desrt, tkamppeter, attente: hey!
[15:30] <desrt> HI!
[15:30] <attente> hi!
[15:30] <didrocks> hope that everybody had some good easter holidays (if any ;))
[15:31] <cyphermox> hey :)
[15:31] <tkamppeter> hi
[15:31] <didrocks> IRC was finely quiet, appreciated to be in a quiet (but lonely) place!
[15:31] <didrocks> anyway: https://wiki.ubuntu.com/DesktopTeam/Meeting/2013-04-02
[15:31] <desrt> didrocks: no vacation for you?
[15:32] <didrocks> desrt: no, planning first to land the 100 scopes
[15:32] <desrt> :(
[15:32] <didrocks> but when it was descoped, planning to land the in dash payment
[15:32] <didrocks> well, at least, quiet days, like no ping in 5 hours, no world record! :-)
[15:32] <didrocks> new*
[15:32] <mterry> :)
[15:32] <didrocks> the wiki is a little bit sparse, do not forget to update it if you have done anything noteworthy ^
[15:33] <didrocks> same with blueprints/WI, do not forget to update them :)
[15:33] <didrocks> ok, let's start
[15:33] <didrocks> Sweetshark: hey!
[15:33]  * Sweetshark reports slacking off for eastern and april fools (that was actually some work). And working on 4.0.2~rc2. I hope everyone tried the 'libreoffice does print on tuesday only' extension. thats all.
[15:33] <jcastro> didrocks: if we want to follow along with smart scopes should we keep the preval PPA around?
[15:33] <jcastro> or will that turn into exploding things?
[15:33] <qengho> - Testing chromium-browser on some specialty ARM hardware. SIGBUS fun.
[15:33] <qengho> - Preparing new chromium-browser stable release for security team.
[15:33] <qengho> - (low priority) Cross-compiling chromium-browser on 64-bit hardware to work around address-space problem at link time.
[15:33] <qengho> - (low) search-exten$ions packaging.
[15:33] <qengho> EOL
[15:33] <didrocks> jcastro: meeting time, will handle more discusion for the end ;)
[15:33] <jcastro> ok
[15:34] <didrocks> thanks Sweetshark (and for the google+ post)
[15:34] <didrocks> qengho: did you heard about qtscripts?
[15:34] <qengho> didrocks: no.
[15:34] <didrocks> qengho: so Qt 5 has a v8 copy
[15:34] <qengho> Of course.
[15:34] <didrocks> qengho: I think the security team is scared about having to maintain 2 copies
[15:35] <didrocks> qengho: can you check with chrisccoulson on this subject?
[15:35] <didrocks> (I think their copy is slightly modified and on older version)
[15:35] <qengho> Will do.  Add this, with webkit, to the externals list, I guess.
[15:35] <didrocks> right ;)
[15:35] <didrocks> thanks qengho
[15:35] <qengho> Fun.  That's all for me.
[15:35] <didrocks> :)
[15:36] <didrocks> v8, webkit
[15:36] <didrocks> small projects :p
[15:36] <didrocks> mlankhorst: hey!
[15:36] <mlankhorst> rt stuff, hard hard hard
[15:36] <mlankhorst> plymouth race continued
[15:36] <mlankhorst> eod?
[15:36] <didrocks> short and concise :)
[15:36] <didrocks> thanks mlankhorst
[15:36] <didrocks> cyphermox: your turn :)
[15:37] <mlankhorst> sorry to be so terse, I was just preparing to leave to think the whole concurrency and rt determinism* problem over while enjoying some nice weather *) https://lkml.org/lkml/2013/4/2/233 *gone*
[15:37] <cyphermox> ah!
[15:38]  * didrocks pulled cyphermox from other channels back here :p
[15:38] <cyphermox> I did the review/prepare (at least until it was waiting to build) for the qtbase/appmenu-qt/dbusmenu-qt uploads
[15:38] <cyphermox> thanks
[15:38] <didrocks> \o/
[15:38]  * cyphermox drops the leash
[15:38] <didrocks> thanks sil2100 for helping on that too ;)
[15:38] <cyphermox> yup, very much!
[15:38] <cyphermox> I also continued working on getting the phablet stuff assigned to me ready for landing
[15:39] <cyphermox> almost done!
[15:39] <cyphermox> today I'm putting a few things aside to try and finally fix that dbusmenu/nm-applet bug.
[15:39] <cyphermox> got a reproducer script now, so with a bit of debugging it should be relatively easy to fix.
[15:39] <cyphermox> EOF
[15:39] <didrocks> excellent :)
[15:40] <desrt> cyphermox: is this the one we were poking at in london?
[15:40] <cyphermox> desrt: yeah
[15:40] <desrt> do you know if the network indicator is on the gmenumodel rewrite list any time soon?
[15:40] <cyphermox> desrt: https://code.launchpad.net/~mathieu-tl/+junk/test-indicator-update
[15:40] <desrt> (i know... you need to do the work for the SRU...)
[15:41] <cyphermox> afaik aruiz or someone is already looking at rewriting a proper indicator
[15:41] <desrt> cool
[15:41] <desrt> thanks
[15:41] <didrocks> btw xnox, robru, cyphermox, mterry: on the spreadsheet I shared on Friday, do not hesitate to poke directly upstream to get every cells to "yes" for the phone stuff. If you get any blocker, do not hesitate to ping me if discussing with upstream didn't help (or if we missed some reverse-deps) ^
[15:42] <mterry> didrocks, I think we need to start to land some of the basic packages like platform-api in the PPA and such that other apps depend on
[15:42] <didrocks> yeah, xnox is doing them, right? ^
[15:42] <mterry> platform-api's packaging branch landed
[15:43] <didrocks> mterry: mind adding to the platform stack and deploying?
[15:43] <didrocks> mterry: I think elements will move stacks once sergio is back from vacations
[15:43] <didrocks> but we can start landing
[15:43] <mterry> k, I can look into it
[15:43] <didrocks> speaking of who… mterry! hey ;)
[15:43] <mterry> - Fixing up some phablet apps and packaging for automerging/autopushing
[15:43] <mterry> - Released new Deja Dup, now with less resource hogging and less everyone-in-the-world-uploading-to-U1-at-midnight-UTC
[15:43] <mterry> - Uploaded a crash fix for sessioninstaller to raring and started a precise SRU for it
[15:43] <mterry> - Filed a merge to add indicators to the UnityNext welcome screen
[15:43] <mterry> - Started a fork of UnityNext to work on next generation unity-greeter (to be later merged back into UnityNext)
[15:43] <mterry> - Ate so many Reeses chocolate eggs...  :-/
[15:43] <mterry> EOF
[15:44] <desrt> mterry: i'm jealous
[15:44] <desrt> (about that last part)
[15:44] <mterry> desrt, too many, I should have written
[15:44]  * didrocks sees "chocolate" and ":-/" in the same sentence
[15:44] <didrocks> doesn't fit!
[15:44] <didrocks> :)
[15:44] <cyphermox> no such thing as too many
[15:44] <didrocks> heh, right
[15:44] <didrocks> thanks mterry :)
[15:44] <didrocks> robru: hey, awake?
[15:44] <desrt> didrocks: maybe not yet.  it's 8:44 there
[15:45] <didrocks> yeah, it's my guess…
[15:45] <didrocks> ok, desrt then, missing some chocolate? ;)
[15:45] <desrt> had my fair share of chocolate, but in the form of mini eggs -- the ones with the hard candy shells
[15:45] <didrocks> sad ;)
[15:46] <desrt> spent some time planning and starting to write the ability to define overrides for default values on gobject properties
[15:46] <desrt> which has been on my list for about a year
[15:46] <desrt> did a lot of optimisations to g_object_new() in the meantime (~30% improvement in common cases) ready to land after being reviewed
[15:46] <didrocks> waow, g_object_new() is this small function almost never used, isn't it? ;-)
[15:47] <desrt> finished up and finally merged a patch for GMenuModel section flattening that hopefully can be used by everyone now to get a common implementation of the functionality (gtkmenu, mac os menus, qmenumodel, even gnome-shell)
[15:47] <desrt> helped attente with his work on the keyboard indicator
[15:47] <desrt> reviewed some patches... including one from larsu to help him with the new sound indicator
[15:47] <desrt> and did some work on action stuff in gio (thanks to attente for reviews there)
[15:47] <desrt> that's all i remember
[15:48] <desrt> oh
[15:48] <desrt> i also spent a long time pressing down a french press _very_ slowly
[15:48] <desrt> and the coffee tastes great
[15:48] <didrocks> bonus point for it :-)
[15:48] <didrocks> thanks desrt
[15:49] <didrocks> attente: here?
[15:49] <attente> didrocks, yep
[15:49] <attente> keyboard indicator is starting to coming together with thanks to desrt and larsu (desktop so far, not phone), has very very basic functionality, and still needs a lot of work and polish
[15:49] <attente> need to talk to mpt and #gnome-design about how the corresponding g-c-c region/input sources panel should look, but may have to postpone this till Oakland
[15:49] <attente> this week will start working on how to implement the phone backend of the indicator, lots of other small things to think about e.g. fcitx integration, icons
[15:49] <attente> EOF
[15:50] <didrocks> keyboard indicator \o/ a long awaited one :)
[15:50] <didrocks> thanks attente
[15:50] <didrocks> hey tkamppeter
[15:50] <attente> thanks didrocks :)
[15:51] <tkamppeter> - Posted MuPDF-printing-related project ideas for GSoC 2013
[15:51] <tkamppeter> - Contacted potential students for participation in GSoC 2013
[15:51] <tkamppeter> - Closed Blueprint https://blueprints.launchpad.net/ubuntu/+spec/desktop-r-cups-bonjour-browsing
[15:51] <tkamppeter> - Reported several laptop-related regressions: Suspend stopped working, mobile broadband stopped working
[15:52] <didrocks> great tkamppeter!
[15:52] <didrocks> ok, my turn I guess
[15:52] <didrocks> * Misc daily release features and fixes.
[15:52] <didrocks> * Prepare and continue on supporting multiple release delivering to the same channel.
[15:52] <didrocks> * Helped and coordinated for touch apps first packaging and evaluation.
[15:52] <didrocks> * Handle de-100ification, but still having the ppa running
[15:52] <desrt> didrocks: you forget seb128 and larsu ;)
[15:52] <didrocks> * Got in my ppa unity + in dash payment for design review and mark's approval in ppa:didrocks/ppa
[15:53] <didrocks> desrt: I hope we'll get larsu, seb128 didn't do anything and he's sleeping right now ;)
[15:53] <didrocks> I heard he even took German holidays!
[15:53] <desrt> :)
[15:53] <desrt> i don't know why that would surprise you
[15:53] <desrt> what happened with the 100 scopes stuff?
[15:53] <didrocks> I'm not :-)
[15:53] <desrt> just decided it was too much work?
[15:54] <didrocks> not good enough quality-wise to be released
[15:54] <desrt> ah.  good reason :)
[15:54] <didrocks> so better to postpone for a release than shipping a broken experience
[15:54] <didrocks> yeah :)
[15:54]  * didrocks is really happy with that decision
[15:54]  * desrt might have guessed ;)
[15:54] <didrocks> despite the huge amount of work :)
[15:54] <didrocks> but well, better in the end, and most of people testing the ppa agrees it's a better experience
[15:55] <didrocks> but it needs a little bit of enhancement
[15:55] <didrocks> design-wise and performance-wise
[15:55] <didrocks> the ppa will stay automagically daily-releasing
[15:55] <didrocks> on top of raring
[15:55] <didrocks> so people using the ppa will get updated and there won't be a conflict with distor
[15:55] <desrt> neat
[15:55] <didrocks> they should as well install the new pinning package: ubuntu-unity-experimental-prevalidation
[15:56] <didrocks> which ensures it will prefer stuff from the ppa
[15:56] <didrocks> jcastro: I think that will answer your questiont ^
[15:56] <didrocks> question*
[15:56] <didrocks> any other question?
[15:57] <mterry> didrocks, for the phablet packaging stuff...
[15:57] <didrocks> yeah?
[15:57] <mterry> didrocks, do we need a bootstrap comment in debian/changelog?   You made some comment before that made me think yes, but I thought those comments were just for switching to inline debian/
[15:57] <didrocks> mterry: good question! :-)
[15:58] <didrocks> so since Friday, this isn't needed for a feature branch
[15:58] <didrocks> as this will land on ubuntu-unity/next
[15:58] <didrocks> it will first take revision 1
[15:58] <didrocks> and then, build from that
[15:58] <didrocks> (adding in the end: * blablabla from rev xxx (ubuntu-unity/next))
[15:58] <didrocks> the 2 sets of commits are not mixed with the "distro ones"
[15:58] <didrocks> so once we get into distro, we'll need it
[15:59] <didrocks> if you think we should wait, it's up to you
[15:59] <didrocks> just be aware that before delivering to distro, we'll need it
[15:59] <mterry> ...  ok
[15:59] <didrocks> mterry: also, we don't need the trick of "at least one commit anymore"
[16:00] <didrocks> of difference
[16:00]  * didrocks likes hacking on quiet days, enabling to do a lot of work :)
[16:00] <didrocks> anymore question?
[16:00] <didrocks> seems not, ok thanks everyone! have a good short week :)
[16:01] <desrt> normal week for canadians :/
[16:01] <didrocks> mterry: xnox is on #ubuntu-devel, you can maybe trick him if needed for reverse-deps :)
[16:01] <didrocks> desrt: like short week is normal? ;)
[16:01] <desrt> no... like no holiday monday
[16:01]  * xnox is not entirely happy with all the pings on this channel =)
[16:01] <mterry> didrocks, post-meeting question.  My unity build-dep branch got rejected by -ci because the version of libunity doesn't exist yet...  How have we gotten around this in the past?
[16:02] <didrocks> mterry: oh, I've been stupid, we should have handle it as a NEW API
[16:02] <didrocks> mterry: like in https://wiki.ubuntu.com/DailyRelease/FAQ#My_package_B_depends_on_a_new_symbol_I_just_added_on_A
[16:03] <didrocks> mterry: see some lines above :)
[16:03] <didrocks> of the previous paragraph
[16:03] <davmor2> hey guys with software-updater it seems to of locked up doing the Preconfiguring packages.... this is todays iso + using software updater for the first time
[16:04] <mterry> didrocks, so bump version of libunity?  This wouldn't help with -ci though, right?  That new version of libunity still won't be in the PPA yet
[16:04] <didrocks> mterry: right, there is a local repository
[16:06] <desrt> AHHH!!!!!!!
[16:06]  * desrt head explodes
[16:06] <mterry> didrocks, I'm leaning towards just building unity twice tomorrow  ;)
[16:06] <desrt> someone needs to die
[16:06] <didrocks> mterry: that's fine with me :)
[16:06] <mterry> desrt, ?
[16:06] <didrocks> mterry: well, the full build
[16:06] <desrt> i just got a book delivered in the mail
[16:06] <didrocks> mterry: and then, you will just kick an unity rebuild
[16:06] <mterry> didrocks, right
[16:06] <desrt> i'm supposd to help review it
[16:06] <didrocks> mterry: you will need something though to build
[16:07] <desrt> it's a new book on gnome3 development
[16:07] <didrocks> mterry: I'm sure we'll find a branch, somewhere… ;)
[16:07] <didrocks> desrt: "nice"? ;)
[16:07] <desrt> i opened the book to the middle
[16:07] <mterry> didrocks, wait it won't rebuild unity if there aren't any new branches?
[16:07] <desrt> very first page is on the topic of gsettings
[16:07] <desrt> "hey!  this is cool!"
[16:08] <desrt> so i read a little.....
[16:08] <didrocks> mterry: no, as there is the filter of "we need something to build"
[16:08] <desrt> and this is what i see:
[16:08] <didrocks> mterry: as you bump the changelog when doing an upload :)
[16:08] <desrt> http://imgur.com/uSk5Fp6
[16:08] <mterry> didrocks, :(  but I'm asking it to manually build.  It should trust me
[16:08] <didrocks> ahah :)
[16:08]  * didrocks sees desrt in despair
[16:08] <mterry> desrt, heh
[16:08] <didrocks> mterry: well, it would trust someone else
[16:08] <desrt> my review of the book, having read one page, is VERY VERY negative
[16:08] <didrocks> mterry: but you? come on! :)
[16:09] <mterry> desrt, you try so hard to crash people's programs, and they still don't get the message
[16:09] <desrt> mterry: SERIOUSLY
[16:09] <didrocks> yeah, it seems crashing wasn't enough :p
[16:11] <mterry> didrocks, OK.  I *think* I just added platform-api to platform.cfg and gallery-app to apps.cfg in head.  Does anybody need to push a button to actually use my config changes?
[16:12] <didrocks> mterry: you need to run cu2d-update-stack
[16:13] <didrocks> mterry: https://wiki.ubuntu.com/DailyRelease/FAQ#Adding.2BAC8-removing_components_to_a_stack
[16:14] <didrocks> mterry: also, you need to specify the generic jobs and the list of package + autopilot jobs to run for the integration tests
[16:14] <mterry> didrocks, ah, fair
[16:14] <didrocks> mterry: do you want that we coordinate/handle that together tomorrow?
[16:15] <mterry> didrocks, are you close to EOD?
[16:15] <didrocks> mterry: more than close, I didn't get time to exercise today, so no break from the past 11 hours :)
[16:15] <mterry> didrocks, OK, go
[16:15] <mterry> :)
[16:21] <davmor2> seb128: Hey dude Who would be the best person to talk to ref software updater/apt?
[16:21] <davmor2> seb128: myself and vila are both hit by the same issue in that it locks up doing precofiguring packages ...
[16:25] <seb128> davmor2, hey, I think your issue could be the bug cjwatson fixed in aptdaemon today
[16:25] <vila> davmor2, seb128: http://paste.ubunu.com/5670927/ with 2 zombies may be relevant
[16:25] <vila> seb128: oh, so trying to upgrade later may be enough ?
[16:26] <seb128> the update should be available
[16:27] <davmor2> seb128: right so update via the terminal and no via software-updater till the fix is in then yes?
[16:28] <seb128> the fix should already in, but otherwise yes
[16:28] <seb128> need to restart, my intel driver is in a weird state
[16:30]  * didrocks is escaping and waves good evening!
[16:33] <davmor2> seb128: Yeap that has pulled in the new apt-daemon by the look of it so I'll try it again tomorrow and see if it works as expected then :)
[16:34] <seb128> davmor2, good
[16:40] <davmor2> seb128: thanks for the info :)
[16:40] <seb128> yw
[16:48] <GunnarHj> seb128: Can you please take a look at my latest comment at bug 1162836?
[16:48] <ubot2`> Launchpad bug 1162836 in lightdm (Ubuntu) "$PATH does not contain /usr/games - /etc/environment not sourced or environment not preserved" [Undecided,Incomplete] https://launchpad.net/bugs/1162836
[16:49] <seb128> GunnarHj, what did you change in the version you asked him to test?
[16:51] <GunnarHj> seb128: I commented the "pam_env.so readenv=1" call at the bottom and added such a call in the beginning.
[16:51] <seb128> GunnarHj, do you think he has a PATH in ~/.pam_environ or something?
[16:52] <GunnarHj> seb128: Then he should have had a problem before as well, shouldn't he?
[16:53] <seb128> GunnarHj, well, not if his userdir is protected
[16:53] <seb128> GunnarHj, but that seems too much guessing at this point, let's wait for extra infos or other reports
[16:53] <GunnarHj> seb128: Aha, you are right.
[16:54] <GunnarHj> seb128: But you agree we wait and see?
[16:54] <seb128> yes
[16:54] <GunnarHj> seb128: Ok, thanks.
[16:54] <seb128> thank you for looking at those bugs ;-)
[16:54] <seb128> mterry, howdy
[16:55] <seb128> mterry, did you get reports about unity-greeter making a sad face if you hit "esc" while entering a password?
[16:56] <mterry> seb128, no?  a couple cycles ago i think we did
[16:56] <seb128> mterry, ok, that started recently, I will file a bug
[16:56] <seb128> mterry, didrocks confirmed it
[16:56] <seb128> the password field vanish if you do that
[16:57] <mterry> seb128, :(
[16:59] <seb128> mterry, I downgraded unity-greeter and still happening, I guess it's a lightdm bug
[16:59] <seb128> mterry, seems like a robert_ancell bug, I will assign to him ;-)
[17:00] <mterry> seb128, or maybe we only noticed it recently
[17:00] <seb128> mterry, no, I do esc at least once a week
[17:00] <seb128> when I'm unsure of what I typed I tend to esc and retype
[17:01] <mterry> seb128, heh ok  :)
[17:09] <seb128> mterry, https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1163456 for info
[17:09] <ubot2`> Launchpad bug 1163456 in lightdm "unity-greeter password prompt vanishes when hitting "esc"" [High,New]
[17:10] <mterry> seb128, thanks
[17:18] <seb128> mterry, ok, and confirmed that downgrading to lightdm 1.5.1 (just the server and gobject lib) fixes it
[17:24] <BigWhale> Is there a way for Kazam 1.4.1 in Raring to become 1.4.2? Before the release?
[17:29] <mitya57> BigWhale: if it's bugfix release, feel free to propose an upload (I see you did some in previous cycles)
[17:29] <mitya57> ... or contact Andrew to get it into Debian and then sync
[17:30] <mterry> seb128, nice.  Yeah, robert_ancell's then  :)
[17:30] <BigWhale> mitya57, it is a bugfix yes.
[17:32] <seb128> mterry, ;-)
[17:33] <seb128> BigWhale, no problem to get a bug fix update still in
[17:34] <BigWhale> seb128, awesome, I made the release a few days ago and everything is in order... I'll bug Ken about it when he's online. :)
[17:35] <seb128> BigWhale, ok
[17:40] <seb128> desrt, the arm builders hate you for some reason
[17:41] <seb128> desrt, the build I tried failed with
[17:41] <seb128> "  /gdbus/codegen-peer-to-peer:                                         g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting."
[17:44] <desrt> huh
[17:46] <desrt> seb128: i wonder if we have some weird threading issues on arm or something
[17:46] <desrt> gdbus is one of the more aggressive threads users....
[17:47] <desrt> and maybe it could be that our atomic operations are not up to snuff or something like that
[17:47] <seb128> could be...
[17:47] <desrt> but why all of the sudden?
[17:47] <seb128> it might be worth trying to kick a build on your nexus
[17:48] <seb128> yeah, not sure what changed
[17:51]  * desrt needs to figure out a good way to get his nexus semi-permanently setup
[17:51] <seb128> dual boot?
[17:51] <desrt> nah
[17:51] <desrt> i mean so i can just have it in my house somewhere and ssh it to when i need to
[17:52] <seb128> ah, I see
[17:52] <seb128> desrt, btw, any chance you could look to https://launchpadlibrarian.net/135746178/buildlog_ubuntu-raring-i386.telepathy-glib_0.20.1-1ubuntu3_FAILEDTOBUILD.txt.gz as well?
[17:52] <seb128> "ERROR:util.c:282:test_utf8_make_valid: assertion failed: (!tp_strdiff (tmp, test[i].target))"
[17:52] <desrt> PASS: test-signal-connect-object
[17:52] <desrt> interesting
[17:52] <seb128> desrt, not sure what changed, the same version used to build, I wonder if it doesn't like glib as well ;-)
[17:52] <desrt> i got a ping on this very topic earlier today
[17:53] <desrt> but it was from a telepathy hacker happy that we finally changed the glib behaviour
[17:53] <desrt> i wonder if this is related
[17:53] <desrt> ie: new behaviour of glib automatically disconnecting signal handlers for objects-as-observer when the object is finalized
[17:54] <seb128> I don't see any obvious commit in http://cgit.freedesktop.org/telepathy/telepathy-glib/log/ that looks like it could address that
[17:55] <desrt> i'll take a look at the testcase
[17:55] <seb128> desrt, thanks
[17:55] <desrt> is it 100% reliable failure?
[17:55] <seb128> xclaesse says he get it on his box since he upgrade to raring
[17:55] <seb128> I didn't test yet
[17:55] <xclaesse> I can reproduce here (raring)
[17:55] <xclaesse> all the time
[17:55] <seb128> but it seems to be
[17:55] <desrt> xclaesse: you're who i'm going to bug to fix it :p
[17:55] <desrt> i guess not...
[17:56] <seb128> lol
[17:56] <desrt> my guess is the glib upgrade causes the issue
[17:56] <xclaesse> desrt, if you fix a nasty gdbus deadlock I'm experiencing atm: https://bugzilla.gnome.org/show_bug.cgi?id=697128 :D
[17:56] <ubot2`> Gnome bug 697128 in gdbus "deadlock in g_dbus_connection_get_type()" [Normal,Unconfirmed]
[17:56] <desrt> xclaesse: lol.
[17:57] <desrt> very well-known gobject bug there
[17:57] <xclaesse> really?
[17:57] <desrt> yes
[17:57] <xclaesse> damned :(
[17:57] <desrt> easy workaround, though
[17:57] <xclaesse> how?
[17:57] <desrt> call g_ensure_type(G_TYPE_DBUS_CONNECTION) from the top of main
[17:58] <desrt> ie: before any threads are created
[17:58] <xclaesse> g_type_ensure() you mean :)
[17:58] <desrt> ya... that one.
[17:58] <desrt> long story short: there is a relatively simple lock-inversion deadlock in gtype.c that will be very difficult to fix
 PASS: test-signal-connect-object --> we had tp_g_signal_connect_object() for a few years ;)
[18:06] <xclaesse> desrt, it's a re-implementation of it using  g_object_weak_ref()
[18:06] <xclaesse> but I'm happy to deprecate that func as soon as we depend on 2.36
[18:09] <desrt> xclaesse: ya... this is exactly what i suspect
[18:10] <desrt> that there is a conflict here
[18:10] <desrt> btw: g_signal_connect_object() is still not threadsafe
[18:10] <desrt> but i think absolutely nobody is using it for this purpose so that's probably OK
[18:38] <rickspencer3> hey guys, QtCreator is not showing up on my launcher :/
[18:43] <seb128> rickspencer3, did that start recently?
[18:43] <rickspencer3> seb128, yeah
[18:43] <rickspencer3> since I dist-upgraded this morning
[18:43] <rickspencer3> seb128, first time since Thursday
[18:44] <rickspencer3> but now the menu integration works, which is nice
[18:44] <seb128> rickspencer3, dpkg -l | grep qtcreator?
[18:44] <rickspencer3> ii  qtcreator                                     2.7.0-0ubuntu1                                                            amd64        lightweight integrated development environment (IDE) for Qt
[18:44] <rickspencer3> ii  qtcreator-doc                                 2.7.0-0ubuntu1                                                            all          documentation for Qt Creator IDE
[18:44] <rickspencer3> ii  qtcreator-plugin-ubuntu                       2.7.0-0ubuntu1                                                            amd64        Ubuntu plugin for Qt Creator IDE
[18:44] <rickspencer3> rc  ubuntu-qtcreator-qt5libs                      0.1-1ubuntu7~raring1                                                      amd64        Qt 5 libraries for Qt Creator
[18:44] <rickspencer3> sorry
[18:44] <seb128> rickspencer3, do you have it pinned in your launcher?
[18:45] <rickspencer3> seb128, no
[18:45] <seb128> oh, ok, so you are starting it and it's not showing in alt-ab/launcher?
[18:45] <rickspencer3> seb128, correct, does not show up in alt-tab either
[18:45] <seb128> Trevinho, ^
[18:45] <seb128> seems like a bamf issue
[18:46]  * rickspencer3 logs bug
[18:49] <seb128> rickspencer3, I somewhat have the feeling that a session restart might fix your issue
[18:49] <rickspencer3> seb128, hmmmm
[18:49] <rickspencer3> seb128, I think I restarted since I dist-upgraded
[18:49] <seb128> still
[18:49] <rickspencer3> let me log the bug and then do the session restart
[18:49] <seb128> bamf didn't change for over 3 weeks
[18:50] <rickspencer3> seb128, should I not log the bug?
[18:50] <seb128> you can
[18:50] <rickspencer3> seb128, yeah, but something changed in Qt, right?
[18:50] <seb128> but I've the feeling it's going to be one of those one time things
[18:50] <rickspencer3> or QtCreator
[18:50] <seb128> qtcreator didn't change
[18:50] <rickspencer3> it's all integrated into the menus know and such
[18:50] <seb128> could be qt yes
[18:50] <seb128> I guess we will know if other people get the issue, or if it's persistent after a session restart for you
[18:51] <rickspencer3> bug #1163522
[18:51] <ubot2`> Launchpad bug 1163522 in Unity "QtCreator Not Appearing in Launcher or Alt-Tab" [Undecided,New] https://launchpad.net/bugs/1163522
[18:55] <rickspencer3> seb128, of course, you were right
[18:55] <rickspencer3> ;)
[18:55] <seb128> rickspencer3, ;-)
[18:55] <seb128> rickspencer3, some days I hate being right on those sort of things :p
[18:56] <seb128> that used to be a frequent issue with bamf, I didn't hit it for a long time (which is good)
[19:44] <cyphermox> bbl