[05:14] <darkxst> pitti, hi
[06:13] <darkxst> pitti, DMB meeting is tonight, can you get to my endorsement today? thanks...
[06:17] <pitti> Good morning
[06:17] <pitti> darkxst: sorry, doing right now; I had a ton of work to finish on Friday
[06:18] <darkxst> pitti, ok, no problem
[06:37] <pitti> darkxst: done
[06:37] <pitti> darkxst: many thanks for your work! I hope you get accpeted, but with that many +1s it shouldn't be a problem :)
[06:44] <darkxst> pitti, thanks
[06:45] <darkxst> pitti, any idea why autopilot fails to introspect gnome-shell properly? I can't even find any code that is gtk specific?
[06:46] <darkxst> (essentially it only picks out the top-level containers, and no children)
[06:46] <pitti> darkxst: not off-hand, I never tried it with gnome-shell; my first idea would be that the thing you want to inspect is using clutter widgets instead of GTK?
[06:46] <darkxst> pitti, yes
[06:47] <darkxst> but the clutter widgets are still gtk no?
[06:49] <darkxst> pitti, walters (upstream) is very interested in having installed tests for gnome-shell
[06:49] <darkxst> right now all they have is screenshots of the test VM
[06:49] <pitti> darkxst: I'm not sure; I thought clutter had its own set of widgets
[06:51] <darkxst> pitti, yes they are unique widgets but still derived from Gtk, atleast as far as I can tell
[06:51] <pitti> hmm; as long as it's a GtkWidget derivative it ought to work
[06:52] <pitti> it does some extra stuff with ATK which most probably won't work for clutter, but that shouldn't break the tree completely
[06:57] <darkxst> pitti, tree is broken, it only picks up the top-level widgets like metaWindow
[07:08] <pitti> darkxst: I briefly looked at gnome-shell now
[07:09] <pitti>   GObject
[07:09] <pitti>    +----GInitiallyUnowned
[07:09] <pitti>          +----ClutterActor
[07:09] <pitti>                +----
[07:09] <pitti> StWidget
[07:09] <pitti>                            +----StButton
[07:09] <pitti> darkxst: so, I don't think that's GTK
[07:09] <pitti> e. g. ./js/ui/workspace.js uses those clutter widgets
[07:12] <darkxst> pitti, how would I teach autopilot about clutter?
[07:13] <pitti> darkxst: it'd need to grow a new backend similar to libautopilot-gtk, which knows how to introspect a widget tree and export it over D-BUS
[07:13] <pitti> so, quite some work
[07:15] <darkxst> oh I see
[07:15] <pitti> lib/GtkNode.cpp does most of that  magic
[07:16] <pitti> i. e. it uses things like gtk_container_get_children() and atk_object_get_n_accessible_children(), iterates over their properties, and exports them to D-BUS
[07:16] <pitti> I guess an autopilot-clutter should be fairly similar to autopilot-gtk, as at least the property stuff ought to be very similar
[07:16] <pitti> but the tree iteration will be different in clutter
[07:17] <pitti> might actually be easier to merge it into -gtk and also support ClutterActor classes
[07:18] <darkxst> yeh I suspect that would be the best solution
[09:02] <Laney> morning
[09:02] <Laney> happy monday ;-)
[09:04] <pitti> hey Laney, good morning
[09:04] <pitti> Laney: and happy birthday!
[09:05] <seb128> heyl Laney pitti
[09:05] <seb128> oh, happy birthday Laney!
[09:05] <pitti> ça va seb128 !
[09:05] <seb128> pitti, très bien, et toi !
[09:06]  * seb128 reads https://lists.launchpad.net/elementary-dev-community/msg02948.html (elementary picking up shotwell to maintain it by forking it...)
[09:06] <Laney> thanks pitti seb128 \o/
[09:06] <Laney> mmm, yeah, saw that
[09:07] <Laney> not sure of the logic behind calling it a fork and doing the rename
[09:07] <Laney> but more development will be good
[09:07] <seb128> they don't want to use the GNOME infra and didn't want to deal with moving it our from there it seems
[09:07] <seb128> well, I wonder what it means
[09:07] <seb128> which one should we use?
[09:07]  * seb128 writes email
[09:08] <Laney> yorba should shut down shotwell @ gnome if it is dead
[09:08] <mlankhorst> morning
[09:09] <Laney> also
[09:09] <Laney> image builds are all broken
[09:09] <Laney> http://people.canonical.com/~ubuntu-archive/livefs-build-logs/trusty/ubuntu/latest/livecd-20140127-amd64.out
[09:09] <seb128> still/again?
[09:10] <seb128> how is unity-control-center ending there?
[09:11] <Laney> hmm
[09:13] <Laney> http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.trusty/rdepends/unity-control-center/unity-control-center
[09:13] <Laney> Depends: dconf-gsettings-backend | gsettings-backend, libc6 (>= 2.2.5), libglib2.0-0 (>= 2.37.3), liburl-dispatcher1 (>= 0.1), bluez (>= 4.36), unity-control-center | gnome-control-center | ubuntu-system-settings, gnome-bluetooth | ubuntu-system-settings
[09:20] <seb128> bah, wifi stopped transfering datas without disconnecting, I was writing an email to the Daniel/Jim and didn't notice before my IRC timedout
[09:32] <seb128> hum
[09:32] <seb128> https://twitter.com/yorbajim/status/426894329064325120
[09:32] <seb128> so it's a real fork
[09:32] <seb128> weird
[09:33] <Laney> yup
[12:16] <dpm> hi Laney, quick question: is there a way for an app to invoke the system settings app and show its accounts page? E.g. it'd be nice for the Reminders app if there is no account configured to have a "Configure Evernote account" button that would launch system settings and the accounts dialog
[12:18] <Laney> dpm: You'll need to ask mardy (or the code) about that one, but it's possible in general to open settings:///system/online-accounts and pass some parameters
[12:18] <dpm> awesome, thanks Laney
[12:18] <Laney> ?foo=bar&something=stuff
[12:19] <Laney> which online-accounts could deal with, to do what you want for example
[12:19] <dpm> I'm not sure if mardy is around, do you happen to know of an app that makes use of it so I could have a look?
[12:19] <Laney> None of our panels do that yet AFAIK
[12:20] <dpm> ok, no worries, I'll try to find out more, thanks!
[12:20] <Laney> also he was active earlier so seems to be aroudn
[12:21] <dpm> ok
[12:21] <Laney> dpm: Looks like it might be supported already
[12:21] <Laney> I see "pluginOptions" in the code
[12:21] <Laney> try ?provider=<someprovider>
[12:22] <dpm> nice!
[12:32] <seb128> mpt, is the "Checking for updates" on https://wiki.ubuntu.com/SoftwareUpdates?action=AttachFile&do=get&target=phone-settings-updates-checking-none.png using normal labels (style, size, etc)?
[12:32] <seb128> same for https://wiki.ubuntu.com/SoftwareUpdates?action=AttachFile&do=get&target=phone-settings-updates-unavailable.png
[12:42] <seb128> Laney, btw I saw your ping about the a-s work, we just need to land stuff together ... did you get any feedback from the telepathy app team on whether they are fine with the changes?
[12:43] <Laney> seb128: hmm, no, should I ping there?
[12:43] <Laney> I was hoping for a code review - it doesn't need to land now (but can, as it still sets the old keys)
[12:44] <seb128> Laney, I guess it wouldn't hurt to ping (boiko?) for a code review (or did you want somebody from desktop to review it)?
[12:44] <Laney> i'll request a review
[12:44] <seb128> hum, it doesn't need to land ... what was needed to land in sync?
[12:44] <seb128> the schemas package and u-s-s?
[12:45] <Laney> ye
[12:45] <Laney> because of Breaks and Depends
[12:45] <seb128> ok, I'm adding that to my to-test-list
[12:46] <Laney> ty
[12:46] <seb128> thanks for the reviews on my mps btw ;-)
[12:46] <Laney> no worries!
[12:46] <Laney> I forgot how to do the bidirectional GSettings stuff properly :(
[12:47] <seb128>     GSettings {
[12:47] <seb128>         onChanged: {
[12:47] <seb128> ...
[12:47] <seb128> ?
[12:48] <Laney> I think Binding { target: myCheckBox property: "checked" value: gsettings.myThing }
[12:48] <larsu> I don't think you need to do the binding thing...
[12:48] <Laney> why not?
[12:48] <seb128> Laney, http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-settings/trunk/revision/411
[12:49] <Laney> hmm
[12:50] <larsu> Laney: I was under the impression you only need that when you can't specify the binding in the object definition (because the object was defined elsewhere, or in c++)
[12:50] <larsu> so CheckBox { checked: settings.myThing } should be enough
[12:51] <larsu> and then onChanged in the settings object for the other way around
[12:51] <larsu> sadly :/
[12:51] <Laney> larsu: It gets unbound chen you change it
[12:51] <Laney> when
[12:51] <larsu> when you change what? The value?
[12:51] <Laney> when you click on it
[12:51] <larsu> huh... why?
[12:51]  * larsu tries out
[12:51] <Laney> it becomes like 'checked: true' and then toggling it externally in GSettings doesn't update it any more
[12:52] <Laney> IIRC
[12:53] <larsu> bah, qmlscene is not working
[12:53]  * larsu hates the qtdeclarative packaging mess
[12:56] <larsu> so ... `qmlscene` searches in /usr/lib/$TRIPLET/qt4/bin
[12:59] <Laney> seb128: Ahh, I see
[12:59] <Laney> that diff doesn't have enough context
[12:59] <Laney> but that's an alright example
[14:03] <seb128> Sweetshark, hey
[14:04] <Sweet5hark> seb128: ho
[14:04] <seb128> Sweetshark, how are you?
[14:05] <mitya57> larsu: Install qt5-default
[14:05] <seb128> Sweetshark, I saw your email, no need to ask for proposed blocks, you can do it yourself by tagging a bug (see https://lists.ubuntu.com/archives/ubuntu-devel-announce/2013-October/001068.html for the details)
[14:05] <Sweet5hark> seb128: pretty fine for being surrounded by four redhat guys in this room ;)
[14:05] <seb128> Sweet5hark, haha ;-)
[14:06] <Sweet5hark> seb128: we should use systemd, or so I heard
[14:06] <seb128> Sweet5hark, rrrrright ;-)
[14:06] <larsu> mitya57: thanks :)
[14:09] <Sweet5hark> seb128: thanks, block-proposed done.
[14:09] <seb128> Sweet5hark, is that really a blocker issue? how is the debugging going?
[14:11] <Sweet5hark> seb128: Just checking. I assume the root cause is the (partial) use of gcj done by rene.
[14:25] <seb128> larsu, did you get any update from Mark on https://bugzilla.gnome.org/show_bug.cgi?id=692931? he attached a slightly modify patch, do you know what's next?
[14:25] <ubot2`> Gnome bug 692931 in Printing "The list of printers should be searchable/sortable" [Enhancement,Unconfirmed]
[14:26] <larsu> seb128: no... let me comment on the bug
[14:32] <seb128> larsu, danke
[15:02] <seb128> attente, hey
[15:03] <kenvandine> mdeslaur, thanks for that xchat-gnome revert... that scrolling problem was driving me nuts!
[15:03] <mdeslaur> kenvandine: yes!
[15:04] <seb128> kenvandine, hey! indeed that was annoying (that and the unity integration being buggy/unread messages not being cleaned leading to segfaults)
[15:04] <kenvandine> segfaults? i hadn't seen that
[15:05] <seb128> for me the unread messages count would get out of sync
[15:05] <seb128> e.g it would stay on e.g 1 #ubuntu-desktop while I had nothing unread in xchat-gnome
[15:05] <seb128> selecting the indicator entry then would make x-g segfault
[15:05] <attente> seb128, hey
[15:05] <seb128> attente, hello, how are you?
[15:06] <attente> seb128, i'm well, and you?
[15:06] <seb128> attente, I'm looking at the spell checking ... do you know if they plan to not support using a spell checking language which is different from the active layout?
[15:06] <seb128> attente, I'm good, thanks
[15:08] <attente> seb128, i'm not sure, but the more i think about it, i'm not sure the design makes sense
[15:08] <attente> seb128, to be able to enable multiple spell checking languages at a time i mean
[15:09] <seb128> attente, why not?
[15:09] <seb128> attente, I've always french and english enabled on my desktop since I use both every day
[15:11] <attente> oh. sorry, i didn't think of that
[15:11] <seb128> ;-)
[15:11] <attente> let's ping bfiller
[15:12] <seb128> attente, ok, I'm fine if they/you change the feature, but in that case the design should be updated
[15:12] <attente> seb128, ok, but you're right, it shouldn't be removed
[15:13] <seb128> attente, yeah, let's just keep the UI there and not displayed, until we have a working backend
[15:13] <attente> seb128, sure
[15:14] <seb128> attente, thanks
[15:15] <seb128> attente, hum, "ASSERT failure in QList<T>::operator[]: "index out of range", file /usr/include/qt5/QtCore/qlist.h, line 462"
[15:16] <seb128> attente, that's on my desktop, I guess it's not handling well the case there is no osk installed/running?
[15:18] <attente> seb128, hmm..
[15:19] <Laney> zzzzzzpandazzzzzzz
[15:23] <didrocks> seb128: hey! (in meetings), just wanted to know if there is something I can demonstrate as a MP for the CI bootcamp?
[15:24] <didrocks> seb128: I'll push the button to show people how it works, but if you can file a request with a line, that would be sweet!
[15:25] <seb128> didrocks, sure
[15:25] <didrocks> seb128: thanks, sorry for the late notice :)
[15:25] <seb128> didrocks, no worry, I wanted to do a landing today anyway
[15:25] <didrocks> great!
[15:26] <seb128> Laney, did you want to ack https://code.launchpad.net/~seb128/ubuntu-system-settings/storage-use-ubuntushape/+merge/203301 ?
[15:26] <Laney> ok
[15:26] <seb128> Laney, so I can sneak it in this landing
[15:26] <seb128> Laney, thanks
[15:27] <seb128> didrocks, CI train table updated
[15:28] <seb128> attente, I also get those warnings "g_settings_get: the format string may not contain '&' (key 'active-language' from schema 'com.canonical.keyboard.maliit'). This call will probably stop working with a future version of glib.
[15:28] <seb128> "
[15:28] <seb128> (that's a desrt thing)
[15:28] <didrocks> seb128: excellent, thanks!
[15:28] <seb128> didrocks, yw ;-)
[15:29] <attente> ah, thanks seb128
[15:29] <seb128> didrocks, did you have a good trip btw?
[15:29] <didrocks> seb128: yeah, uneventful, everything was fine, thanks!
[15:29] <seb128> great ;-)
[15:29] <Laney> did you get the train?
[15:30] <Laney> the TGVs are quite nice
[15:32] <didrocks> yeah, TGV until Disney
[15:32] <didrocks> and then Eurostar
[15:33]  * Laney loves the TGV jingle
[15:33] <Laney> sncf
[15:43] <larsu> seb128: those are very easy to fix (I put that warning in recently)
[15:43] <larsu> oh, attente seems to be on it already...
[15:46] <seb128> larsu, I'm pondering patching the warning out before release, it's creating log noise/spam for issues than are not real ones (at least not for this cycle)
[15:47] <seb128> larsu, but yeah, we can as well fix easy stuff on the way meanwhile ;-)
[15:48] <Laney> I'd rather gather the 'spammy' issues and fix them
[15:48] <larsu> seb128: spam as in lots of messages from single apps? If so, can I convince you to take a patch that only shows the warning once per running app?
[15:48] <Laney> if you turn off the warning then break the functionality it comes out of the blue
[15:48] <Laney> it effectively removes the deprecation period
[15:49] <seb128> Laney, well, as said "before release", the same way we turn apport launchpad reporting off the week before release
[15:49] <seb128> larsu, no, rather I found like half a dozen apps throwing those warnings on my system and I'm using a very small portion of the archive
[15:49] <larsu> but people developing their apps on a stable ubuntu won't get the warning, then
[15:50] <larsu> and I really think they should. That's why I put it in in the first place...
[15:50] <seb128> choices are
[15:51] <seb128> - spend time fixing non user visible issues to not have the log spam, in detriment of spending that time on user visible issues
[15:51] <seb128> - have some log spamming, with the IO/wakeup issues it creates
[15:51] <seb128> - turn off the warnings
[15:51] <larsu> seb128: https://bugzilla.gnome.org/show_bug.cgi?id=692931 is committed to master. Thanks for the ping
[15:51] <ubot2`> Gnome bug 692931 in Printing "The list of printers should be searchable/sortable" [Enhancement,Resolved: fixed]
[15:51] <seb128> larsu, thanks \o/
[15:52] <seb128> well, anyway, glib warnings are not a big issues, it's more annoying than anything else
[15:53] <larsu> I'm all for option (2). How many apps are we talking about?
[15:53] <seb128> I've no idea, and I'm not sure if we can archive grep for those?
[15:53] <seb128> could be 10 like it could be 100
[15:53] <seb128> glib has some thousand rdpends
[15:54] <larsu> hm, 113 occurences in ~/.cache/upstart for me...
[15:55] <larsu> seb128: grep "g_settings_get.*&" should get the vast majority of cases
[15:56] <seb128> larsu, http://codesearch.debian.net/search?q=g_settings_get.*%26
[15:57] <larsu> hm, okay. Maybe I was a bit quick there :/
[15:57] <larsu> the '&' must be between double quotes
[15:57] <larsu> http://codesearch.debian.net/search?q=g_settings_get.*%22.*%26.*%22
[15:58] <Laney> BAD GNOME-TERMINAL
[15:58] <larsu> ya...
[15:58] <Laney> that's all I have if I grep my logs
[15:59] <seb128> seems it's the main offender indeed
[15:59] <seb128> u-s-s has one issue but attente is on it
[16:02] <larsu> seb128: has been fixed in g-t: https://git.gnome.org/browse/gnome-terminal/commit/?id=d8d71e0c1e7a8fb723becaa270334171e6730fc2
[16:02] <seb128> Laney, ^ want to have a look at backporting that?
[16:03] <Laney> could do in a bit
[16:03] <larsu> Laney, seb128: it's also on 3-10: https://git.gnome.org/browse/gnome-terminal/commit/?h=gnome-3-10&id=ac62dbbda2630d1d963d399317d59cf7b78dc7f2
[16:04] <seb128> larsu, danke
[16:05] <jcastro> hey kenvandine
[16:06] <jcastro> I am seeing this in trusty: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/793450
[16:06] <ubot2`> Launchpad bug 793450 in indicator-datetime (Ubuntu) "Calendar doesn't show today's date until opened a second time today" [Medium,Confirmed]
[16:06] <jcastro> should I reopen or make a new one or ... ?
[16:08] <kenvandine> jcastro, new bug
[16:09] <jcastro> kenvandine, can you help me put it on whatever radar you guys use? :)
[16:09] <kenvandine> jcastro, i don't follow the indicators very closely anymore, seb128 ^^
[16:10] <didrocks> seb128: mind if I remove the 3rd MP?
[16:11] <seb128> didrocks, :-(
[16:11] <didrocks> there is an unicode error for me, will fix it
[16:11] <seb128> didrocks, unicode error?
[16:11] <didrocks> yeah in the command message
[16:11] <didrocks> commit*
[16:11] <seb128> didrocks, you mean the mp triggers a bug?
[16:11] <seb128> didrocks, or did I screw up something?
[16:11] <didrocks> there is a bug
[16:11] <seb128> didrocks, but sure, drop it, we can do another round later
[16:11] <didrocks> I need to fix it :)
[16:11] <didrocks> ok ;)
[16:11] <seb128> ok
[16:11] <didrocks> thanks!
[16:11] <seb128> no worry
[16:12] <seb128> yw ;-)
[16:12] <seb128> jcastro, talk to charles_
[16:12] <jcastro> charles_, hi!
[16:12] <seb128> but I think it's on the LTS backlog
[16:12] <charles_> hi jcastro
[16:12] <charles_> oo, I picked up an underscore over the weekend
[16:12] <jcastro> yeah so I think I have this: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/793450
[16:12] <ubot2`> Launchpad bug 793450 in indicator-datetime (Ubuntu) "Calendar doesn't show today's date until opened a second time today" [Medium,Confirmed]
[16:12] <jcastro> but in general, when I click on the datetime indicator, the highlight over the day is never correct
[16:13] <jcastro> at first I thought, ok whatever, minor bug, but this week I scheduled something incorrectly due to the widget so I was hoping to put it on someone's radar
[16:13] <ali1234> yeah the calendar always has whatever day i booted selected
[16:14] <ali1234> it's always done that since it was created afaik
[16:14] <jcastro> and sometimes it's like the date from 2 weeks ago
[16:14] <ali1234> well i reboot about once every two weeks, so yeah
[16:14] <ali1234> currently it says 17 jan here, and i have 9 days uptime
[16:14] <jcastro> eventually it gets the right day, but then it comes back wrong after a boot or suspend.
[16:15] <seb128> jcastro, I'm going to make sure we fix it before the LTS ;-)
[16:15] <ali1234> if i select a different day it always remembers that day and keeps it highlighted
[16:15] <jcastro> seb128, is there anything you need from me? Still need a new bug or ?
[16:16] <jcastro> seb128, any wart/bug is acceptable in the calendar _except_ the wrong date. :)
[16:17] <Laney> the text at the top is right :P
[16:17] <ali1234> yes, it is. just the highlighted day is wrong
[16:17] <jcastro> yeah
[16:17] <charles> jcastro, what's going on there is that the calendar doesn't know to snap to today's date when the menu is popped down
[16:17] <jcastro> but the highlight is orange on the day, it's impossible to miss.
[16:17] <ali1234> why does it even let you highlight a day?
[16:18] <charles> when we decoupled from GTK+ we lost the ability to know when the popdown is happening, so we need to replace that with something else
[16:18] <seb128> jcastro, no need of new bugs/info no, it's a well known/understood issues, we discussed it a few time, it just needs somebody to sit down and fix it
[16:18] <jcastro> ali1234, yeah I don't get that either, why it allows me to click on any day and highlight it.
[16:18] <jcastro> seb128, awesome, thanks!
[16:19] <ali1234> also why does it flicker weirdly when i click on a day?
[16:20] <seb128> ali1234, oh, yeah, it shifts on the left and right again it seems
[16:20] <seb128> let's hope charles has some bugfixing time before the LTS ;-)
[16:21] <ali1234> tried to screen record the flicker but it happens too fast
[16:22] <seb128> ali1234, it's more visible if you display the week numbers on the left
[16:23] <seb128> (the setting is not picked dynamically btw)
[16:23] <ali1234> is that in the control panel? because i can't use that
[16:24] <charles> seb128: this particular bug isn't so much a datetime bug as it is u-p-s or ido
[16:24] <charles> seb128: datetime is just where it becomes visible
[16:24] <seb128> ali1234, yes (and gsettings)
[16:25] <seb128> charles, the menu is reconstructed when the selection change?
[16:25] <ali1234> looks like it. the whole menu disappears for like 1 frame
[16:25] <charles> indirectly, yes. selection change re-queries EDS for an updated appointment list starting from the new selection point
[16:25] <charles> that's done async
[16:26] <charles> when that query comes back, we rebuild the appointments section of the menu
[16:27] <charles> seb128, (to be pedantic: ...actually in the BMRIROT the appointment section doesn't get rebuilt unless the new set of appointments actually differs from the old.)
[16:27] <seb128> charles, nice, I already like the BMRIROT ;-)
[16:28] <seb128> charles, do you want people to test that branch or do you prefer to work a bit more on it before that happens?
[16:30] <charles> seb128: it should be ready for you to poke around by  my EOD
[16:30] <seb128> charles, great, I'm going to give it a try tomorrow then
[16:30] <charles> seb128: right now there are merge conflicts from the unity panel changes that landed last week and I'm getting everything sync'ed
[16:30] <charles> seb128: after that...yes, testing would be much welcomed
[16:30] <seb128> k
[16:31] <seb128> added to my todolist
[16:31] <charles> \o/
[16:31] <seb128> ;-)
[16:31] <charles> I should be careful what I wish for ;-)
[16:34] <ali1234> what is u-p-s btw?
[16:34] <ali1234> oh wait, unity-panel-service
[16:35] <ali1234> i'm not actually using that, but if it requires changes to the xfce equivalent we'll need to make them
[16:49] <chrisccoulson> qengho, are the builds in https://launchpad.net/~canonical-chromium-builds/+archive/stage ready to test and go out?
[16:49] <qengho> chrisccoulson: test, yes.
[16:49] <chrisccoulson> qengho, cool, thanks
[16:49] <qengho> chrisccoulson: I don't have "go" from #webapps yet.
[16:49] <chrisccoulson> heh
[16:50] <qengho> Having decent ARM builders is *so so so* nice.
[16:50] <chrisccoulson> qengho, who gives you the go from webapps btw?
[16:50] <charles> jcastro, ali1234, seb128: wrt the calendar date bug, https://bugs.launchpad.net/unity/+bug/793450/comments/31
[16:50] <ubot2`> Launchpad bug 793450 in Indicator Date and Time "Calendar doesn't show today's date until opened a second time today" [Medium,Triaged]
[16:52] <seb128> charles, thanks
[16:53] <seb128> chrisccoulson, hey, are you going to look at firefox/arm|ppc|ppc64 in trusty or do you need help there?
[16:54]  * chrisccoulson hides
[16:54] <seb128> lol
[16:54] <chrisccoulson> seb128, for arm64, a patch got uploaded whilst i was away, but it got dropped again because it was never checked in to bzr
[16:54] <qengho> chrisccoulson: alex-a usually.
[16:55] <chrisccoulson> seb128, but the patch is absolutely huge, has no owner, no upstream bug and hasn't had a review from anybody in any case
[16:56] <chrisccoulson> it needs somebody committed to maintaining a nearly 100kB patch, and driving it upstream :)
[16:56] <seb128> chrisccoulson, well, we need to get the trusty version updated one way or another
[16:56] <chrisccoulson> for ppc / ppc64, i've no idea
[16:56] <chrisccoulson> we should just disable it on those architectures. even if it builds, it'll be virtually unusable without a jit
[16:56] <seb128> chrisccoulson, it worked on other series for ppc, is that a toolchain issue? can we build with old gcc?
[16:57] <seb128> or that
[16:57] <chrisccoulson> i've not looked at the ppc failure
[16:57] <seb128> chrisccoulson, do you think you can do that in the next weeks or do you need help?
[16:57] <chrisccoulson> the same applies to arm64 as well really - we might get it to build but with no arm64 assembler in the jit it's going to be completely unusable
[16:58] <chrisccoulson> i don't think i'll have much time in the next couple of weeks, and i'm sprinting next week too
[16:59] <seb128> chrisccoulson, ok, thanks for the summary, I'm going to see if I can find anyone to help there
[16:59] <chrisccoulson> thanks
[17:41] <seb128> night
[17:53] <dpm> oh, Laney, forgot to say earlier on, happy birthday! :)
[17:55] <Laney> thanks dpm!