=== duflu_ is now known as duflu === Optichip` is now known as Optichip [04:06] good morning :) [04:49] Bonjour tout le monde [04:55] bonjour pitti [04:57] larsu: wow, you are early :) [04:57] larsu: in my defense, I was in the garden, collecting snails [04:58] pitti: haha, breakfast? [04:58] larsu: je n'est suis pas français ! [04:59] pitti: I figured now that you can speak french, ... === tvoss_ is now known as tvos === tvos is now known as tvoss === thumper is now known as thumper-afk [06:28] pitti, hey! [06:35] Grr. Why does logind conflate VTs and local sessions? [06:35] hey darkxst, hello RAOF [06:35] pitti: Good morning! [06:40] pitti, any chance you could look at the retracer sometime soon? [06:45] pitti: Do you know any way of interrogating logind's internal state to see which session it considers active? [06:46] Particularly, I want to know why my one and only session isn't considered active. [06:48] RAOF: "loginctl show-session c2" (or any session identifier from "loginctl") shows the details [06:50] darkxst: ah, sore spot.. [06:51] Morning! [06:55] pitti, we still get way more data from raring+ppa than saucy, but its all mostly useless! [06:57] pitti: Yeah, but that doesn't show which session logind thinks *is* active. There's only one session listed, and it's not active [07:02] Mirv: hello! [07:03] RAOF: "loginctl" shows all sessions, so if none is active then there just isn't a registered PAM session for that VT [07:03] pitti: Correct! My session isn't associated with a VT! [07:03] RAOF: sorry, I mean not a foreground one, which is the current VT [07:03] RAOF: ah right, that's like ssh then [07:04] Mirv: do you have a moment for some stacks reviews? [07:04] Mirv: https://code.launchpad.net/~sil2100/cupstream2distro-config/fix_extra_pkgs_next/+merge/177512 [07:05] Mirv: the QA stack is missing ibus, but I guess I'll have to discuss this with seb, as the 'extra package' won't be needed once the new ibus goes out of -proposed [07:05] Mirv: so for now all the other stacks [07:05] RAOF: although, that apparently is also active; ssh is just "remote"; so, no immediate idea then [07:05] Mirv: would be grateful for a quick review and approval since I want to move the stacks ;) [07:08] Why does logind even have the ability to activate a session? [07:08] RAOF: that's what logind managers have used for years (well, it's ConsoleKit equivalent back then) to switch between multiple sessions [07:08] login managers or things like indicator-session [07:09] sil2100: hi! [07:09] sil2100: I had https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/add_libubuntu-application-api1_to_platform/+merge/177509 already waiting for you :) [07:09] to fix my stack [07:09] Yeah, but you can't switch to an arbitrary logind session. [07:10] This is particularly annoying because logind is going to be *unable* to switch between our sessions. [07:10] Beacuse a switchable-session-is-a-VT, and all our sessions are going to be on a single VT. [07:10] Mirv: ok, hm, so maybe we can approve your branch and then mine [07:11] Mirv: since my branch has the same change, it shouldn't conflict ;) [07:11] sil2100: right, that should work I think [07:11] pitti, or perhaps I could just get the scripts you use for the retracer? [07:11] Mirv: approved yours ;) [07:11] darkxst: sure, there's nothign particularly magic about them [07:12] Mirv: once it gets in, approve mine if +1 [07:12] darkxst: this is basically a checkout of lp:apport, plus a checkout of https://code.launchpad.net/~ubuntu-archive/apport/lp-retracer-config/ for the per-ubuntu-release config [07:12] darkxst: this branch also has the crontab which I'm using in the data center [07:14] sil2100: yeah, will check and +1 [07:15] sil2100: thanks :) [07:16] RAOF: right, so we either need to disable user switching from the session indicator, or teach logind about Mir's idea of VT multiplexing; then it needs an alternate way of getting notified about what the current session is and how to enumerate them (i. e. Mir sending out some signals) [07:17] I feel it might be simpler to just incorporate that functionality into lightdm [07:17] But for now I need to help prepare Zoë for dinner. [07:17] or that [07:17] that would also avoid heavy patches against logind, and keep the Ubuntu specific bits together [07:18] RAOF: logind still needs to know about that though, to be able to assign correct device ACLs [07:18] pitti: checking [07:18] pitti: ctrl+alt+f1 goes to console as expected (no suspend) [07:19] asac: yes, I mean if you close the lid on VT1, does it suspend? [07:20] pitti: ok will try in a bit [07:20] asac: so you can reproduce suspend errors in X? [07:21] pitti: last two days whenever i closed the lid it never suspended [07:21] always have to remember to push the menu [07:22] ok trying console and lid [07:22] pitti: yeah. on console it works [07:22] on x it just turns off the screen [07:22] asac: just to cover all bases, what do these show? [07:22] gsettings get org.gnome.settings-daemon.plugins.power lid-close-ac-action [07:22] gsettings get org.gnome.settings-daemon.plugins.power lid-close-battery-action [07:23] pitti: Unless lightdm applies the ACLs :) [07:23] asac@thinki:~$ gsettings get org.gnome.settings-daemon.plugins.power lid-close-ac-action [07:23] 'suspend' [07:23] asac@thinki:~$ gsettings get org.gnome.settings-daemon.plugins.power lid-close-battery-action [07:23] 'suspend' [07:23] RAOF: sure :) [07:23] pitti: ^^ [07:23] asac: -> /msg [07:24] good morning everyone [07:28] Morning! [07:28] Mirv: it's in, can you approve my branch? [07:28] Laney: are you planning to go with gstreamer 1.2 for this release? planned release date is somewhere in september just in time for gnome 3.10 [07:30] pitti: Seriously, though, if (in the magical future) lightdm is already handling session tracking and switching it doesn't seem as though there's any reason to keep logind around. [07:30] sil2100: yep, redeployed platform and approved your commit for the two others which you can then redeploy [07:30] \o/ [07:30] Thanks [07:30] RAOF: quite a lot of upstream software depends on it, though; so maybe not in a default ubuntu installation, but as dependencies [07:31] pitti: libsystemd-login is just a dbus wrapper around logind, right? [07:31] Mirv: so I'm leaving platform up to you and dealing with all the other stacks [07:32] RAOF: yes [07:32] So all we'd need to do is expose a compatible dbus interface? [07:33] good morning [07:33] "all" [07:33] RAOF: in principle, yes [07:33] if lightdm emulates that in terms of Mir sessions, that'd be fine [07:33] that's going to be no small task, though (all the cgroup handling, etc.) [07:34] sil2100: right, ok [07:34] logind exposes all that cgroup handling? [07:34] RAOF: i. e. it's d-bus plus a compatible cgroup handling [07:34] I thought that was basically an implementation detail? [07:34] Ah. [07:35] well, it is, but (1) we still want that, and (2) quite a lot of software checks for /run/systemd/seats (or similar) [07:35] RAOF: mostly JavaScript/Python/etc. stuff which doesn't want to or can't link to the lib [07:35] Yay. [07:35] but reproducing the /run state files is rather simple [07:36] RAOF: we actually switched away most upstream software from checking the cgroups, to checking the /run files [07:38] Ah, well. There's still the transitional case we need to care about, with both VTs and Mir sessions. [07:38] That makes patching logind more palatable. [07:39] RAOF: would gnome not get a similar problem when switching to wayland? [07:39] RAOF: or does that use different VTs somehow? [07:39] pitti: GNOME is not planning to use a system compositor; they'll run a Wayland compositor on each VT. [07:40] ah [07:40] so they wouldn't have that problem [07:40] good morning desktopers [07:41] Right. [07:41] They also don't get the benefits ☺ [07:42] They might eventually decide that they want them, and then they will indeed hit exactly this problem. [07:42] sil2100: I wonder why platform still compiles about the package.. bzr pull:d the -config, redeployed, reran with foo [07:42] seb128: (already asked Laney before but maybe you know too?) are you planning to go with gstreamer 1.2 for this release? planned release date is somewhere in september just in time for gnome 3.10 [07:43] slomo, hey, we were discussing it recently with kenvandine (he said the new version would be nice/useful for some of the stuff on the touch image) [07:43] slomo, I'm not sure though, I've little confidence on the gstreamer release schedule ... wasn't 1.2 initially scheduled for around GNOME 3.8? === tvoss is now known as tvoss_test === tvoss_test is now known as tvoss [07:44] seb128: well, for the ubuntu touch work that jhodapp is doing you'll need it anyway ;) but that's independent i guess? [07:45] seb128: but yes, our release schedule is not very reliable unfortunately :) however we're almost there now finally, what is missing right now is just some more testing and then it can get the 1.2.0 label [07:47] slomo, right, that's what Ken said, jhodapp's work need it, we could do with a ppa though [07:48] pitti: In less frustrating news, feel like sponsoring colord 1.0.2-1? :) [07:48] RAOF: sure! still no DM? [07:49] I'll get around to sending that email sometime :) [07:49] seb128: hey! how are you? [07:50] seb128: ok, so what information do you need to decide? i think it would make sense to either switch now or after the next ubuntu release to give it enough testing for ubuntu [07:51] RAOF: expected? [07:51] dpkg-source: info: local changes have been recorded in a new patch: colord-1.0.2/debian/patches/debian-changes [07:52] RAOF: i. e. it generates a debian/patches/debian-changes [07:52] pitti: Yup. You should find that debian-changes contains your glib deprecation fixes. [07:52] didrocks, hey, good, you, having fun at the sprint with everyone? not too much beer drinking? ;-) [07:52] RAOF: ah, not using real patches for that? [07:53] seb128: not too much beer, lot of discussions, we'll see :) [07:53] pitti: For things which are upstream I cherry pick. [07:53] seb128: btw, I honored the promise to work on ubuntu-system-settings during the flight [07:53] RAOF: ah, upstream pulls [07:53] seb128: small ui changes: https://code.launchpad.net/~didrocks/ubuntu-system-settings/system-update-improvment/+merge/177371 [07:53] do you mind giving a look? [07:53] pitti: That way I don't have to notice when we pass a revision which contains them :) [07:53] sil2100: once/if merged, do you mind kicking the stack again with this? ^ [07:53] RAOF: ack, sbuilding now; I just wanted to confirm, as they sometimes slip in accidentally [07:53] small UI changes to have a better demo :) [07:54] seb128: ah, FYI, I'll be on a meeting during the team meeting, I asked sil2100 to lead it :) [07:54] \o/ [07:54] didrocks: ok! [07:54] thanks sil2100 ;) [07:55] didrocks, will review, thanks ;-) [07:55] didrocks, ok [07:56] seb128: thanks to you ;) [07:56] seems it's fresh in France as here [07:57] 19°C this morning [07:57] going to get warmer again tomorrow though [07:58] RAOF: uploaded; NB that we are past DIF, so you'll need to sync manually if you want this in saucy [07:58] pitti: There's no particular reason not to have it; I'll sync away! [07:59] seb128: ok, anyway, let me know if you need any more information or have decided something :) [08:00] slomo, sorry, IRC is a bit busy... [08:00] slomo, when do you plan to land the new one is unstable? [08:01] slomo, also ... is there any known problem with the current 1.1/things to worry about? [08:02] morning [08:02] slomo: I was a bit put off by the advice against adopting it in your announcement the other day :-) [08:03] seb128: unstable once the API is stable, i can't guarantee yet that there will be no changes in anything newly added... but it's unlikely. otherwise, i'm not aware of any regressions that are left, the last one was fixed right before 1.1.3 :) [08:03] seb128: and in general it's all in bugfix and cleanup mode now, no bigger new features are going to happen before 1.2 [08:03] I think we'll probably start out with a PPA [08:04] the packaging should be easier anyhow since some of the plugin moves get to be undone [08:04] Laney: well, you ship glib 2.37 too, right? the warning in my announcement mail goes along the same line ;) [08:04] ugh [08:04] heh [08:04] didrocks: the apps stack has some problems, so I will probably have to fill in a bug and get it fixed before it can get released today ;/ [08:05] slomo: Also I don't really know about it but it'd make me happy if jhodapp's stuff could have some upstream review before we include it ;-) [08:06] slomo, ok, I think it's reasonable for us to consider it once it's unstable [08:06] not sure if he's submitted it yet or is close to [08:06] I'll start work on PPAing it anyway quite soon [08:06] (upstream, not seen his stuff yet) [08:07] Laney, thanks [08:07] Laney, good morning btw ;-) [08:07] hallo! [08:07] Laney: agreed, i think it's still full of bees :) i didn't look at it closer yet [08:09] seb128: ok, what's exactly the reason for depending on it being in unstable? my reason for not putting it there is basically the same as for glib 2.37, if it wasn't for the possible small API changes i would just put it there ;) [08:10] slomo: ok, please keep bfiller aware [08:10] It's being conservative [08:10] slomo: sorry, I mean sil2100 ^ [08:10] slomo, it has a cost to follow unstable series, we do it for glib because we use some of the new features and we have desrt on board who can help with the issue [08:10] issues [08:10] we have experience with unstable glibs, and also can abuse ryan for fixes if necessary [08:10] slomo, we have less expertise on gstreamer [08:11] so one path with that is ppa, people self select for testing, if no major problems then distro [08:11] helps insulate us a bit [08:12] seb128: ah, makes sense :) thanks for explaining [08:13] slomo, yw [08:16] pitti, how do the need-retrace tags get set? === tkamppeter_ is now known as tkamppeter [08:19] darkxst: through the blob uploaded to Launchpad, in apport/crashdb_impl/launchpad.py _generate_upload_blob() [08:19] darkxst: i. e. they are there when creating the bug [08:21] pitti, ah right, our bugs are already tagged ;) [08:21] darkxst: yes, you mostly need to create a config file for your project instead of the distro (add a stanza to the config file in lp-retracer-config) [08:22] darkxst: and use 'project': 'ubuntu-gnome', insteaed of 'distro': 'ubuntu' (see /usr/share/doc/apport/crashdb-conf.txt.gz) [08:23] darkxst: crash-digger has a --crash-db option where you supply the new db you are adding (instead of using the "default" one in crashdb.cnof) [08:24] pitti, thanks, I think i got it now [08:29] Mirv: are you on the platform stack failure? [08:30] seb128, is there a list of setting backend for Ubuntu Touch that we need for 13.10? [08:30] Mirv: since I don't want to release the related stacks before knowing if all is ok [08:31] seb128: hello! [08:31] sil2100, hey [08:31] rickspencer3, define "setting backend"? [08:31] seb128: how's the ibus release from -proposed going? [08:31] sil2100, it's in saucy proper since yesterday [08:31] seb128, I dunno, like things that need to have settings for them [08:31] \o/ [08:32] seb128: awesome then! So it seems out otto images are still outdated [08:32] But good, it means tomorrow all will be ok already [08:32] rickspencer3, the prd has the list, it's basically the ones listed on the "phone" column of https://wiki.ubuntu.com/SystemSettings [08:32] thanks seb128 [08:33] rickspencer3, yw [08:37] seb128: have you started doing the suggesting I made to about-connect-check-for-update? [08:37] suggestion === Ivanka_ is now known as Ivanka [08:38] Laney, I did it yesterday, but not the shared js way, just trying the getByName [08:38] ok, would have done it myself otherwise [08:38] Laney, but it's 1 extra object and 10 lines of code, I'm not convinced of the value of the change... [08:39] Mirv: ok, redeploying the stack ;/ [08:39] Laney, I don't expect us to rename pages [08:39] Laney, I think I'm going to end up doing the shared js stuff to avoid the extra churn in the plugin itself ;-) [08:40] :-) [08:40] Mirv: re-running the platform stack after redeployment now [08:41] sil2100: ok, I think should be good now [08:41] sil2100: I just forgot the -U [08:42] rusty from vacation still :) [08:42] ;) [09:06] seb128: can you check/approve the package rename packaging change of http://10.97.0.1:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_platform-api_0.18.3+13.10.20130730-0ubuntu1.diff ? libplatform-hardware-api1-hybris became libubuntu-platform-hardware-api1, and libplatform-api1-hybris -> libubuntu-application-api1 [09:10] seb128: soo, bug 1204449 is blocking on bug 1196263 and I agree with upstream that the reporter is likely seeing ghosts there. Is there any way to go ahead with this SRU (which is fixing critical bugs) despite these vague and nonreproducable claims? [09:10] Launchpad bug 1204449 in libreoffice (Ubuntu) "[SRU] LibreOffice 4.0.4 for Ubuntu 13.04 (raring)" [Undecided,Confirmed] https://launchpad.net/bugs/1204449 [09:10] Launchpad bug 1196263 in libreoffice (Ubuntu) "Libre Office 4.0 Paper Tray" [Undecided,Incomplete] https://launchpad.net/bugs/1196263 [09:12] Sweetshark, can somebody test the scenario he describes and confirm if it works/doesn't work for them? [09:15] seb128: If someone has a printer with multiple trays it might give hints. tkamppeter maybe? [09:15] Sweetshark, yes, try asking tkamppeter or maybe in the London office? [09:16] seb128: note though that you cant proof the absence of errors. He might still claim it does not work with _his_ printer. [09:17] seb128: also he hasnt even confirmed that it wasnt a problem in 4.0.2 as released with raring. [09:17] seb128: are you ready for some quick packaging ACKs? ;) [09:17] Sweetshark, well, I wouldn't block the SRU on it, but it would still be good to check if the problem he points is not an obvious breakage [09:18] sil2100, sure, trying to review Mirv's one but I don't understand all the renames there [09:18] Mirv, it would help to have changes help a bit more than "to match debian guidelines" [09:18] seb128: larsu: http://ubuntuone.com/0u8ueGOxYL3eRu4Gti9PHo =) i'll see if I can find where ubiquity's theming is going absurd =) [09:18] seb128: ok, in the meantime I'll prepare the rest and send you the links [09:18] Mirv, why are the replaces/breaks versionned rather than just forcing to uninstall the old names? [09:19] xnox, hehe [09:19] sil2100, thanks [09:19] xnox: first absurdity is that it loads the theme in every draw() event... [09:20] xnox: s/theme/background pixmap/ [09:20] seb128: more information at https://code.launchpad.net/~ricmm/platform-api/package-match-sonames/+merge/175181 [09:20] Mirv, thanks [09:21] Mirv, looks fine to me, +1 [09:22] seb128: ok, thanks [09:23] seb128: All he claims is "it used to work with the 4.0 ppa on 12.04 at some point". So it could be a/ it doesnt work on 12.04 but works on 13.04 b/ he had some other ppa breaking his stuff c/ it was never working on LibreOffice 4.0.2, but only on e.g. 4.0.0 (which is not what we released with raring) .... [09:24] seb128: in the meantime! http://10.97.0.1:8080/view/cu2d/view/Head/view/WebApps/job/cu2d-webapp-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-webapps-qml_0.1+13.10.20130730-0ubuntu1.diff [09:24] seb128: this will be a buuusy week for you... ;) [09:24] Sweetshark, well, as said don't block on that, but if it's easy to check if what he describe is a bug or not you might want tkamppeter/somebody at the office to give it a try and confirm it's a bug (even if it's not a regression it might still be a valid bug) [09:25] sil2100, yeah, thanks didrocks for letting me with some extra pings :p [09:25] sil2100, what's the rational for the arch any -> hardcoded list change there? I though we didn't want to list archs manually anymore? [09:26] seb128: \o/ [09:27] all worked like according to the plan :) [09:27] :-) [09:27] just want to show to rickspencer3 I'm not slacking off :p [09:27] Mirv: tell me once platform and sdk are published [09:27] seb128: I think there's no real rationale besides making sure that powerpc is not supported ;) [09:28] o/didrocks [09:28] will you be joining us in the spa? [09:28] O_O [09:28] didrocks, do you know if there is a reason we should still use hardcoded arch lists (I think you said Ken has to roll back on not listing ppc because colin was having issues)? [09:30] rickspencer3: taking my towel :) [09:30] tssss [09:30] seb128: some packages needed for colin to be able to unblock for webcreds (accounts-settings AFAIK) [09:30] seb128: but that should be temporary and not needed anymore AFAIK [09:31] didrocks, so http://10.97.0.1:8080/view/cu2d/view/Head/view/WebApps/job/cu2d-webapp-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-webapps-qml_0.1+13.10.20130730-0ubuntu1.diff feels wrong [09:31] arch: any is better so that the day we start having armel64… [09:31] sil2100, -1 from me, please change back to arch: any or give the rational in the changelog [09:31] Mirv: since platform got published, could you publish SDK? [09:31] seb128: ACK [09:31] seb128: I don't see anything justifying it for me [09:31] so -1 as well [09:31] rickspencer3: oh btw did you get the memo about touch fixes? [09:31] mlankhorst, no [09:32] mlankhorst, yes! [09:32] I saw that you had an xorg for me to try and stuff [09:32] yeah [09:32] but I hadn't had a chance yet [09:32] mlankhorst, are you still waiting for me? [09:32] rickspencer3: no, but if you want working touch at least it's possible, but hard to get back in raring because it probably requires a newer version of onboard [09:32] Mirv: I already published all the standard stacks [09:32] mlankhorst, raring is dead [09:32] ;) [09:33] we are on saucy [09:33] put raring out of your mind [09:33] saucy could work, I'm waiting for the backport to 1.14 [09:33] rickspencer3: hah, when I still have to land it in the LTS? :P [09:33] mlankhorst, yes [09:33] but for now, our focus still needs to be on Ubuntu Touch for 13.10 to the maximum extent possible [09:33] yeah [09:34] Mirv: I jump out to the store - please publish SDK in the meantime! [09:34] mlankhorst, so, I worked around this bug by not using the touchscreen with Chromium ;) [09:35] yeah the fixes will be in saucy, was just hoping upstream would merge it to 1.14 so I didn't have to do it manually, it's quite a big patch series.. [09:39] seb128: oh, there sure might be valid bug -- otherwise I would not have upstreamed that one. Note though upstream currently has 131 unresolved bugs related to printing (of 251 with resolved bugs). Also note that there are at least two related bugs: One is a (fixed) 3.3->3.4 regression, the other one is reported against 3.6 and was fixed for 4.1: https://bugs.freedesktop.org/show_bug.cgi?id=61186 ... [09:39] Freedesktop bug 61186 in Printing and PDF export "Print dialog ignores saved settings from Printer Settings + more" [Normal,Verified: fixed] [09:40] Sweetshark, right, as said, don't block the SRU on it in any case [09:40] ... so without the reporter confirming it still doesnt work in 4.1.0 its actually likely a dupe of fdo#61186 .. [09:40] sil2100: yeah, on my list [09:40] seb128: yep ;) [10:18] hm looks like upstream has some more fixes that might help without having to update unboard.. [10:24] Laney, thanks for approving the dash privacy setting mp ... days/months, I've no idea when design is going to iterate on that, seems safer to just stick with that meanwhile ;-) [10:25] sure [10:25] Laney, oh, new glib out btw, in case you feel like you need a break from system settings at some point ;-) [10:25] I do feel like that :P [10:25] ;-) [10:25] I'm just making datetime use NM for status for now and then I'll do that or gst for a bit [10:26] lucky you, I was looking at fixing xinput :P [10:27] shortly I have to go to the police station and give a statement about my Crime Of The Century :-) [10:29] hah [10:29] did you steal your own bike? [10:30] no comment [10:30] srsly though I told them I thought it wasn't worth anybody's time to do that for the theft of one skewer but they insisted [10:32] oh that [10:33] well it's probably for insurance and/or their own numbers [10:33] that's why I reported it [10:33] didn't expect to have to do anything other than phone up [10:33] maybe there will be an armed response [10:36] seb128: ah, here's the arch revert for webapps: https://code.launchpad.net/~sil2100/unity-webapps-qml/arch_any/+merge/177559 (if you have a moment) [10:37] sil2100, approved by comment, you need to change the MR status though, I'm not in the right team to do it [10:37] seb128: thanks! === Ivanka_ is now known as Ivanka [10:41] sil2100: hum [10:41] did you relaunch system-settings? [10:42] didrocks, I did, why? [10:42] didrocks, slangasek wanted a landing [10:42] didrocks: the merge wasn't merged in back when I checked, so no [10:42] seb128: did you check it wasn't already launched? [10:43] didrocks, no, nobody else than me is usually dealing with settings stuff [10:43] seb128: not sure what will happen, I think I stopped the prepare job before it was uploaded in the ppa [10:43] didrocks, aren't you supposed to be busy in IoM? ;-) [10:43] we'll know in 2 minutes [10:44] didrocks, jenkins flagged a changelog merge back as approved [10:45] seb128: yeah, I think even if you rebuild, it would have been blocked in the publisher step [10:45] didrocks, I would appreciate if you let me know next time you republish settings [10:45] seb128: I asked sil2100 first to look at that, so you did relaunch without warning him as well :) [10:45] (but I admit I didn't tell him before relaunching it) [10:47] didrocks, well, we already had a landing today, I didn't see you ping sil2100 about redoing one ... anyway no problem, I will check next time, I was just 100% nobody else would touch because until now nobody ever did look at settings (out of normal published when the stack is un manual publishing) [10:47] didrocks, sorry for the conflict [10:47] seb128: no worry at all, we're both guilty :) [10:47] seb128: TBH, the system would have handled it [10:48] I'm just unsure about launchpad enabling binary copy of a superseeded package [10:48] cool [10:48] then, the second publish would have failed [10:48] (as the version in distro would have been != from the version when prepare run) [10:48] it would just have been an useless build in the ppa [10:49] but TBH, I won't challenge that today and test in production :p === MacSlow is now known as MacSlow|lunch [11:54] jibel: hi! Just reminding, https://code.launchpad.net/~sil2100/otto/fix_1203809/+merge/176692 <- the fix has been made as you recommended it ;) So I guess it would be a quick review now! [11:59] seb128: larsu: the menuitem gets the same height as the submenu, thus the menubar ends up having the height of the tallest submenu =( i'm not sure why the menuitem gets such large height. Maybe it's horizontal/vertical error? and/or homogenous somewhere? well I didn't manage to shrink it, with request_size. [12:00] xnox: this is unrelated to my fix, it looks the same to me without [12:00] xnox: I'll have a look later today [12:01] larsu: well, I uploaded your fixes to at least get back the indicators. so it will be on tomorrow's daily cd, to test live / easier. [12:01] larsu: thanks a lot for your branch =)))) !!!! [12:02] xnox: cool, thanks for the quick upload === MacSlow|lunch is now known as MacSlow === dednick is now known as dednick|lunch [13:02] chrisccoulson: I can help with Firefox. [13:03] qengho, hey, how is the chromium build on saucy going? [13:03] chrisccoulson: I don't think I'm immersed in its culture enough to adopt, but I want to learn it some. [13:04] seb128: Er, linker bug avoided, I think. Only time will tell. [13:04] seb128: turnaround time is far too long. [13:04] qengho, when do we get an upload? ;-) [13:05] seb128: saucy-proposed should be halfway through building. [13:05] qengho, hum, there was no chromium-browser upload since the 24 ... or you mean you are ppa testing it before archive upload? [13:07] seb128: Hrm, I meant actual distro. Let me look around. [13:07] qengho, https://launchpad.net/distros/ubuntu/+source/chromium-browser [13:08] https://launchpad.net/ubuntu/+source/chromium-browser/28.0.1500.71-0ubuntu1.13.10.1 is the most recent upload and it failed armhf and i386 [13:09] mpt, working on the SIM Services page, what should we display if there is no SIM card? [13:10] i assume disable the listitem [13:10] but should we display something like SIM Services (No SIM found) ? [13:17] sigh, found out that in xserver.git most recent commit broke the test, then found out both the test and the commit were broken :/ [13:23] kenvandine, yes, insensitive. https://wiki.ubuntu.com/PhoneApp?action=diff&rev2=5&rev1=4 [13:23] seb128: Okay, well, I thought I had it sponsored and uploaded a day ago. I guess I was wrong. When you said to chrisccoulson that you saw him uploading chromium, I thought that was him uploading chromium-browser_28.0.1500.71-0ubuntu3 . [13:24] qengho, oh no, that was the previous uploads a week ago, sorry for the confusion [13:24] mpt, thx [13:25] chrisccoulson, ^ can you sponsor it? [13:25] seb128: Where do you see the feed? Do you sip from the firehose saucy-proposed mailing list? [13:25] qengho, yep, saucy-proposed ... I just glance over the title in the morning and a few time a day, it's a bit of traffic but just reading the package names in the subject list is taking like a minute [13:55] another u-s-s snapshot? [13:59] Laney, I ran a rebuild, not noticing that didrocks did one, but that was before lunch and didrocks was supposed to have killed it [13:59] qengho, thanks for the offer :) [13:59] oh and it just took that long to grind through [13:59] didrocks, ^ did you trigger a new one? [14:00] Laney, that's my guess, but it's just guessing... [14:00] qengho, one thing i need to try and figure out is why the tests don't run in saucy: https://jenkins.qa.ubuntu.com/job/saucy-adt-firefox/ [14:00] they do run ok in raring: https://jenkins.qa.ubuntu.com/job/raring-ppa-adt-mozillateam_firefox_next-firefox/ (same package) [14:01] Laney, ok, that might make you happy, uploaded the new poppler ... that's giving plenty of opportunity to change our mind, by doing rebuild/build fixes, after looking at qt for too many hours [14:01] hehe [14:01] I just started looking at glib [14:02] * Laney types d p u t f t p - m a s t e r really slowly [14:10] chrisccoulson: I'm new to autopkgtest, but I'll poke at it. [14:10] qengho, thanks. don't worry about it too much if you have other stuff to do though :) [14:11] chrisccoulson, hey, how are you? [14:11] seb128: yeah, I didn't see anything merged and I wanted to have the stack green [14:11] seb128: but obviously, I was wrong :p [14:11] seb128, yeah, not too bad thanks. how are you? [14:11] didrocks, I'm good thanks [14:12]