/srv/irclogs.ubuntu.com/2013/06/14/#ubuntu-desktop.txt

=== Guest26134 is now known as jbicha
jbichajcastro: of course, half the Desktop team is either French or Canadian or French-Canadien00:09
jbichamaybe more than half, I don't really keep track00:09
mdeslaurjbicha: make sure you don't mix up all three by accident, that would be an insult :)00:37
jbichanow I'm confused00:41
=== jbicha is now known as Guest85286
=== Guest85286 is now known as jbicha_
pittiGood morning04:04
=== duflu_ is now known as duflu
bkerensacyphermox: is there any readily available tool to chart/time how long it takes for a wifi connection to occur?06:52
czajkowskiI'd be very surprised to see cyphermox online at this hour06:57
Sweesharkmoin!07:53
czajkowskiSweeshark: good morning07:53
=== tkamppeter_ is now known as tkamppeter
* Sweeshark cries. the amd64 ppa-build has been canceled. While I dont know for sure, I assume it was someone seeing it had run out of disc space again.07:56
SweesharkAnd I already removed the subsequentchecks/dev-install and some 100MB from the src-tarball (the latter should have freed some 200MB).07:56
SweesharkThe more I think about it, the more I come to assume, that it has little to do with changes in libreoffice (which after all killed the big binfilter stuff recently, so should still be smaller than it was before that).07:58
czajkowskiSweeshark: do you know which build machine it was07:58
czajkowskiI know we are just getting one restarted there07:58
Sweesharkczajkowski: no, maybe https://launchpad.net/~bjoern-michaelsen/+archive/libreoffice-nattytest2/+build/4669264 helps you see which one it was?07:59
SweesharkIm assuming now its more the dependencies of libreoffice each growing in size like cancer since we lost the CD-image limit.08:01
Sweesharkczajkowski: grapping for that straw (that the box was just rebooted), Ill reschedule that build optimistically now.08:02
czajkowskiSweeshark: it ran out of disc space and hung is why just asked in -ops08:02
Sweesharkczajkowski: sigh08:02
Laneyhappy happy friday08:03
* Sweeshark look at the line in the rules file saying "ENABLE_JAVA=Y" with a lecherous gaze ...08:05
czajkowskiLaney: peeka boo08:05
Laneyhallo thar08:06
Laneylast day?08:06
czajkowskiyarp08:06
czajkowskibeen busy so far08:06
* Laney sheds a tear08:06
czajkowskiLaney: bah I'll see you in two weeks ;)08:06
Laneytrue that08:07
Laneyis the new job working from home too?08:07
czajkowskioh hell ya :)08:09
czajkowskiwill go to the office for the first few weeks reguarly it's still in london08:09
czajkowskibut I also have about 30-40% of my time to travel through EMEA08:09
Laney:O08:10
sil2100seb128: hi! Would you mind if I gave you some packaging diffs to take a look at? Since before publishing stacks, we need to have an archive admin to ACK the packaging changes08:12
sil2100seb128: it's all in one diff file usually08:13
seb128sil2100, sure, go for it08:14
sil2100seb128: SDK stack: http://10.97.0.1:8080/view/cu2d/view/Head/view/SDK/job/cu2d-sdk-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_dee-qt_3.0daily13.06.14-0ubuntu1.diff08:14
sil2100seb128: and settings stack for now: http://10.97.0.1:8080/view/cu2d/view/Head/view/Settings/job/cu2d-settings-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-system-settings_0.1daily13.06.14-0ubuntu1.diff08:15
sil2100Both changes are sane from my point of view08:15
seb128sil2100, the dee-qt one is buggy08:17
seb128sil2100, the added copyright states08:17
seb128"either version 3 of the License, or08:17
seb128+ (at your option) any later version."08:17
seb128but the license is GPL-3 and not 3+08:17
seb128so you either need to add the + or drop the "or any later version"08:17
sil2100Ah, right, I see that now, hm08:18
sil2100Let me check that package08:18
seb128sil2100, the settings one is fine (it's coming from me so I will not complain :p)08:18
sil2100seb128: ok, need to fix the copyright then, since it's GPL3 not 3+08:19
sil2100seb128: but publishing the settings stack ;)08:19
seb128sil2100, you can publish dee-qt but please fix in trunk08:19
seb128sil2100, e.g that's a typo, not worth having to retest/respin the stack08:20
seb128just make sure it's fixed for the next landing08:20
sil2100ACK :)08:20
sil2100seb128, Mirv: https://code.launchpad.net/~sil2100/dee-qt/fix_copyright/+merge/16936208:22
seb128sil2100, approved08:24
sil2100seb128: thanks! Another quick one, the misc stack: http://10.97.0.1:8080/view/cu2d/view/Head/view/Misc./job/cu2d-misc-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_gnome-control-center-unity_1.3daily13.06.14.1-0ubuntu1.diff/*view*/08:24
seb128sil2100, looks fine to me08:26
sil2100Thanks :)08:26
Laneyfixing g-c-c ftbfs08:30
Laneylooks like goa dropped symbols "that were not part of the public API"... yeah...08:31
Mirvsil2100: ..appr.. damnit08:32
Mirvsil2100: https://code.launchpad.net/~timo-jyrinki/qtubuntu/dont_install_test_files_update_standardversion/+merge/16935508:33
seb128Laney, I fixed it in the vcs already08:34
Laneyoh ok08:34
seb128Laney, I didn't upload because I was working on some other changes and wanted to batch them08:35
seb128Laney, sorry I fixed that some days ago but I figured out there was no point to upload the build fix by itself if another upload was coming08:35
Laneynm08:35
seb128did I forget to push?08:35
Laneyno, I just didn't pull08:35
seb128ok ;-)08:36
Laneywell, rather I worked from apt-get source ¬_¬08:36
Laneyyou revealed my secret reluctance to use our branches08:36
LaneyBLAST08:36
seb128I'm looking at libgadu and gmock-test (just stating so we don't dup work)08:36
seb128lol08:36
sil2100Erm08:37
sil2100Mirv: so the -examples package is not valid?08:37
Mirvsil2100: yeah well it was either adding that or removing it altogether, and apparently Ken knew it was just a test binary (I also sweeped the device image yesterday and nothing uses it, but still kept it around in my branch)08:39
Mirvmakes sense, though08:39
sil2100Mirv: ok, looking good, approving!08:39
Mirvthx!08:41
sil2100seb128: another one, network stack: http://10.97.0.1:8080/view/cu2d/view/Head/view/Network/job/cu2d-network-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_telepathy-ofono_0.2daily13.06.14-0ubuntu1.diff08:41
sil2100seb128: we're missing multiarch here, but we'll be adding that soon08:41
seb128sil2100, seems fine to me08:42
sil2100seb128: ok! Publishing, I think that once I do that, telepathy-ofono will land in NEW, since it's possible that it has not been released08:43
sil2100So it might need NEWing08:43
seb128ok08:43
seb128I can review it when it's in there08:43
sil2100Mirv: I'll re-run the platform stack once the location-service fix gets in08:53
sil2100Mirv: and publish it (along with the media stack) ;)08:54
sil2100Mirv: once that is done, I hope you won't mind I finally do some appmenu coding ;p?08:56
Mirvsil2100: thanks. any appmenu stuff is greatly appreciated, considering we really won't do Qt 5.1.1 upload (arrives probably around August) with the old patch! :)09:03
Mirvsil2100: you may want to check out the Qt 5.1 beta1 I've made available in a PPA, or just take the latest upstream 'stable' (5.1) branch09:04
seb128Laney, mono is unhappy about the new automake ... want to have a look?09:04
seb128Laney, btw do you know if there is any plan to follow debian on mono 3.0.6?09:04
Laneyseb128: I'll pass it on and maybe look later09:05
seb128ok09:05
Laneyand well, not right now - it's still a bit broken09:05
Laney(having said that: https://bugzilla.xamarin.com/show_bug.cgi?id=9324)09:13
ubot2`bugzilla.xamarin.com bug 9324 in packaging "cannot build with automake 1.13" [Normal,Resolved: fixed]09:13
seb128Laney, seems like an easy fix at least ;-)09:15
seb128looking at gtk2-engines09:15
LaneyI'll try to dig them out09:16
Laneyis someone fixing the indicators? :-)09:19
pittianyone with an nvidia or ati graphics card here?09:19
Laneyi'll do mono then gst09:19
Laneypitti: yes, I have nvidia09:19
pittiLaney: would you mind giving me the output of "udevadm info --export-db" on that system?09:19
pitti(as user is fine)09:20
Laneypitti: http://paste.ubuntu.com/5764102/09:20
pittiLaney: cheers09:20
Laneykein problem!09:21
sil2100seb128: do you know if there is anything else I need to do for you to be able to NEW a package that's new and not existing yet in the universe?09:22
seb128sil2100, no, which one needs newing?09:22
sil2100seb128: telepathy-ofono - it was part of network stack, published an hour ago ;)09:23
sil2100(through the publish job)09:23
seb128sil2100, it was not published, at least it's not showing up on https://launchpad.net/ubuntu/saucy/+queue?queue_state=0&queue_text=09:24
pittiLaney: oh crap, that doesn't have a vendor/product name any more for your card09:24
pittiLaney: just for completeness, that I can make sure I fix ubuntu-drivers-common properly, "ubuntu-drivers debug" output please?09:25
sil2100seb128: strange, the publish job says all is ok: http://10.97.0.1:8080/view/cu2d/view/Head/view/Network/job/cu2d-network-head-3.0publish/lastSuccessfulBuild/artifact/packagelist_rsync_network-head/*view*/09:25
sil21002013-06-14 08:43:49,758 INFO Writing packagelist_rsync_network-head for being able to rsync from main machine09:25
sil2100list is: [('qa', 'head')]09:25
sil2100I wonder if Didier was doing anything else...09:26
Laneypitti: yep, http://paste.ubuntu.com/5764117/09:26
pittiLaney: thanks²09:26
Laneykkpp09:26
pitti*chuckle*09:27
pittiLaney: double negation!09:28
seb128sil2100, can you retry? the lillypilly checkout was not uptodate09:29
seb128sil2100, https://wiki.ubuntu.com/DailyRelease/FAQ mentiones "Then, ping an archive admin so that he pulls the modification on lillypilly for the second-safety check process. "09:29
seb128sil2100, so maybe ofono was not in the safe-to-publish list yet on that side09:30
seb128sil2100, I've pulled so it should be fine if you retry09:30
pittiLaney: what does "udevadm test-builtin hwdb /devices/pci0000:00/0000:00:01.0/0000:01:00.0" say for you?09:31
sil2100seb128: ok, re-publishing then09:31
Laneypitti: calling: test-builtin09:32
Laneyerror reading /etc/udev/hwdb.bin: No such file or directory09:32
Laneyload module index09:32
Laneyunload module index09:32
sil2100seb128: I thought that pinging the archive admin should be done after publishing09:33
pittiLaney: ack, thanks; I smell an udev bug for me09:33
Laney:-)09:33
seb128sil2100, well the publishing didn't happen because you have a new package which was not in the security-check-list09:33
seb128sil2100, there is a second list on the other side of the publisher that checks that we don't publish things we are not meant to09:33
seb128sil2100, that's to avoid having somebody e.g adding "linux" to the ps jenkins and having you guys upload the kernel when you are not supposed to have upload rights for that09:34
sil2100k09:35
sil2100hm, the re-run of the publisher probably did not upload anything09:37
sil2100Since I think it thinks it already did previously ;/09:37
sil21002013-06-14 09:32:08,518 INFO Copying from https://api.launchpad.net/devel/~ubuntu-unity/+archive/daily-build (Release) to https://api.launchpad.net/devel/ubuntu/+archive/primary (Proposed) for saucy series09:38
sil2100Although it says this?09:38
seb128sil2100, get a fake commit if you need a version bump?09:39
sil2100seb128: I wonder if a commit that just adds a changelog entry is enough09:47
seb128sil2100, should be09:47
sil2100seb128: ok, I'll try to re-run the stack09:51
seb128ok09:51
sil2100seb128: we have an issue in the build scripts, I need to fix that first, sorry about the wait...10:03
seb128sil2100, no worry, I'm not blocked or waiting on that, I will just review when ready ;-)10:04
mhr3sil2100, btw did you have a chance to look at the soname bump for unity-core? a check would be appreciated, i basically just ran sed :)10:10
seb128sil2100, do you know what happened to the unity SRU for raring? it vanished from the queue10:10
seb128did infinity reject it?10:10
Laneyseb128: See the #-release backlog10:10
Laneyit broke because it expired from launchpad10:11
Laneythey need to start using a staging PPA for SRUs10:11
seb128Laney, I just looked to http://irclogs.ubuntu.com/2013/06/14/%23ubuntu-release.html and don't have a match for unity10:11
Laneylook for compiz10:11
seb128oh ok10:11
seb128pffff10:12
seb128that's what happen when the SRU team takes over a month to review SRUs for our main desktop10:12
seb128that's ridiculous10:13
sil2100seb128: uh, didn't hear anything about it10:13
* seb128 goes to read what happened on the TB discussion 10:13
seb128sil2100, you will need to get it republished10:13
seb128and hope infinity takes less than a month this time to review it10:13
sil2100Mirv: ^10:14
pittiLaney: FYI, filed as bug 119094710:15
ubot2`Launchpad bug 1190947 in systemd (Ubuntu) "[udev] missing vendor/product names of devices (missing hwdb.bin)" [Medium,Triaged] https://launchpad.net/bugs/119094710:15
seb128pitti, speaking about systemd, is that logind that suspends my box on lid close nowadays?10:16
Laneycheers10:16
Laneynot that I noticed any symptoms of this bug :P10:16
pittiseb128: it's meant to be, anyway; but our g-s-d power plugin also does it; bug 118051310:16
ubot2`Launchpad bug 1180513 in gnome-settings-daemon (Ubuntu) "lid close actions are ignored laptop always suspends" [High,Triaged] https://launchpad.net/bugs/118051310:16
pittiseb128: what needs to happen is that g-s-d power inhibits logind's suspend-on-lid (that's done in 3.8, but not in our 3.6)10:16
Laneyah it manifests itself in s-p-gtk10:17
seb128pitti, do you know if anyone has filled a bug about "shouldn't suspend during shutdown"? I picked "shutdown" yesterday, closed my lid and found out later than it suspend on the plymouth shutdown logo10:17
pittiLaney: bug 118677710:17
ubot2`Launchpad bug 1186777 in ubuntu-drivers-common (Ubuntu) "Does not show vendor/model name any more" [Undecided,In progress] https://launchpad.net/bugs/118677710:17
Laneygot it10:17
seb128pitti, when I woke it up I had 3 seconds of plymouth and shutdown finished10:17
pittiseb128: I don't know about that one, no10:17
seb128ok10:17
seb128is systemd the right component to bug?10:18
pittiseb128: I guess we need to do that in systemd-shim10:18
pittias logind otherwise doesn't know that a shutdown has been requested already10:18
seb128k, I will talk to desrt when he's online10:18
seb128pitti, danke10:18
sil2100seb128: hmmm... I re-published telepathy and hm10:24
sil2100seb128: I still can't see it in NEW10:24
sil2100seb128: do we need to wait a moment?10:24
seb128sil2100, the queue updates every 5 minutes let's wait a few minutes10:26
seb128sil2100, otherwise we will need didrocks on monday I guess10:26
Laneyis libappindicator going to daily release soon?10:30
Laneythe build failure fix is in trunk10:30
Laney(it's funny how the fix for that problem everywhere is to disable it)10:31
sil2100seb128: telepathy-ofono is there \o/10:31
seb128sil2100, good ;-)10:32
seb128Laney, same for some of the indicator-* I guess10:33
sil2100Laney: so, indicators... let me remember the status10:34
seb128Laney, well, at the same time we have no hurry to fix those build issues, knowing that the next upload will build anyway10:34
seb128looking to indicators stack on jenkins there are some "scary" changes in there10:34
seb128e.g port the new format10:35
Laneydidn't check the others10:35
sil2100Laney: I think we need to release indicators and unity at the same time10:35
Laneylibappindicator looks kind of small-ish since the last release10:35
sil2100Which would basically mean we'll have to fix up HUD first for the tests to pass10:35
Laneydon't know what the latest change is though10:35
seb128http://10.97.0.1:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/10:35
Laneyseb128: still it's good to have stuff building in the archive if possible10:35
seb128http://10.97.0.1:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_libindicator_12.10.2daily13.06.14-0ubuntu1.diff10:36
seb128for example10:36
seb128+  [ Lars Uebernickel ]10:36
seb128+  * Merge lp:~larsu/new-indicator-file-format IndicatorNg: update10:36
seb128+    indicator file format The old file format had some shortcomings: (1)10:36
seb128+    It was impossible to efficiently reuse a menu for different10:36
seb128etc10:36
Laneyright10:37
seb128sil2100, telepathy-ofono NEWed10:44
sil2100seb128: thank you!10:44
seb128yw ;-)10:45
Laneyseb128: did you look at bluetooth yet?10:46
seb128Laney, sort of, I glanced at the log, seems like a case of "turn of Werror", but I didn't start on it ... if you want to fix it, please do ;-)10:47
Laneyhaha, OK10:47
seb128I'm doing some piloting10:47
seb128I missed my shift earlier in the week, I was too busy on system settings :p10:47
LaneyI think it's going to be that XID has a different type10:47
seb128well, it has also "variable not used" warnings10:48
seb128turn off Werror :p10:48
Laneythose are warnings10:49
Laneyfound https://git.linaro.org/gitweb?p=people/tomgall/oe/meta-openembedded.git;a=commitdiff;h=9c657f0e6975a283fcc8f3b748c006882fab961a10:49
sil2100seb128: quick question - are we providing powerpc in the archive?10:49
Laneyyes10:50
seb128sil2100, what's the real question? we do but qt5-declarative isn't available on it because v8 is not10:50
sil2100seb128: ah, ok, I was asking because dbus-cpp (a package that will need to be NEWed pretty soon) has broken tests on powerpc and fixing them is non-trivial right now, so I wanted to disable those for powerpc10:51
sil2100seb128: and have been wondering if that would be acceptable by distro10:51
seb128it's not ideal, but I wouldn't block things on ppc tests10:52
=== MacSlow is now known as MacSlow|lunch
desrtseb128: sup?11:10
seb128desrt, hey11:10
seb128desrt, <seb128> pitti, do you know if anyone has filled a bug about "shouldn't suspend during shutdown"? I picked "shutdown" yesterday, closed my lid and found out later than it suspend on the plymouth shutdown logo11:11
pittihey desrt11:11
desrtare we sending shutdown requests via systemd?11:11
desrtor just calling 'shutdown'?11:11
pittivia logind11:12
desrtso i added logic to systemd-shim about this....11:12
desrtsurprised to hear that it's not working11:12
desrtthe code is pretty simple....11:13
desrthttps://github.com/desrt/systemd-shim/blob/master/src/power-unit.c#L4511:13
desrtwhen it starts a shutdown/reboot it sets 'in_shutdown' to TRUE11:14
desrtif in_shutdown is true, further suspend/hibernate requests are ignored11:14
mitya57seb128: thanks for uploading qt4!11:16
seb128mitya57, yw11:16
seb128desrt, pitti: my auth.log has "00:05:24 localhost systemd-logind[930]: System is powering down."11:22
seb128so shutdown was indeed done correctly through logind11:22
desrtperplexing11:26
seb128is there any debug info I can provide if that happens again?11:26
seb128don't worry much, it's a minor issue, I was just wondering wth my suspend led was blinking after shutdown :p11:27
desrti wonder if maybe the shutdown was going via the other route instead....11:27
desrtpitti: did you remove the fallback path to pmutils in logind?11:27
desrts/shutdown/suspend/11:27
desrtseb128: was the shutdown taking a really long time?11:32
desrtthe other thing i remember is that the shim quits after 10 seconds of inactivity....11:32
desrtso shutdown, wait 10 seconds [shim quits], close lid11:33
desrtin that case, that variable would be back to false again and the suspend would go through11:33
seb128desrt, no, 5-10s, the user session took some 5 seconds to close, I saw the plytmouth logo some seconds later and closed the lid at this point11:33
desrtseb128: 5-10s is still on the order of 10s, maybe....11:33
seb128could be yes11:33
seb128if that from the moment the shutdown action is called?11:34
desrtyes11:34
seb128could well be 10s then yes11:34
seb128the user session took almost 10s to close11:34
desrtsounds right, then11:34
desrti'll do a patch to keep the thing alive forever when shutting down or rebooting11:34
seb128(hate how logout is slower than login)11:34
desrti bet that's the issue11:34
seb128thanks ;-)11:35
pittidesrt: yes, I did11:43
pittidesrt: thanks!11:43
=== MacSlow|lunch is now known as MacSlow
tedgseb128, Are we changing BlueZ versions in Saucy?13:25
seb128tedg, not planned13:25
tedgK13:25
tedgseb128, Do you think that's going to hit in Terrified?13:25
seb128tedg, we discussed it around february, but bluez5 requires a newer version of linux that the one that was used for some touch images13:26
seb128and it was not a priority13:26
seb128we can still re-evaluate if there is a need13:26
tedgK, I've got no reason to change, just wanting to know for making sure we get porting on the schedule.13:26
seb128but there was nothing in 5 that we needed for the phone v113:26
tedgWe might need to for T because of NM using it and not wanting to support an older version for the LTS.13:27
seb128tedg, I doubt we will update before v1 if there is no strong reason, we don't have resources to waste13:27
* ogra_ doubts touch images will get any newer kernels in T13:27
seb128tedg, let's see when that happens, meanwhile upstreams can port their code13:27
tedgYup, okay.13:28
cyphermoxbkerensa: there isn't. you'll probably just want to take the times from syslog14:04
=== m_conley_away is now known as m_conley
=== Aww is now known as EvilAww
=== Sweeshar1 is now known as Sweetshark
=== EvilAww is now known as Aww
seb128jbicha, hey, I saw you tried some bugs about the sound recorder, bug #1159744 is about the issue14:28
ubot2`Launchpad bug 1159744 in gnome-media (Ubuntu) "replacment for gnome-media" [Undecided,Confirmed] https://launchpad.net/bugs/115974414:28
seb128jbicha, basically a contributor ported it to gstreamer1 but the GNOME guys said the component was deprecated and would want to take the patches/make new releases it seems14:29
jbichaseb128: I'm dropping gnome-media for Ubuntu GNOME, if that fork gets packaged I don't know if we'll include it or not; I mean how often do people need a Sound Recorder app anyway?14:30
seb128quite some people use one apparently14:31
seb128it has been requested by oems to our oem team in the past and we had quite some bugs reports about it not working since it's broken14:31
Laneywe should probably remove it meanwhile14:55
seb128Laney, or just apply the patch from the contributor (would avoid to have to package a new source etc)15:03
seb128on that note I'm out for some exercice, be back in ~1h15:03
Laneyit doesn't seem to really be a patch ...15:04
seb128it's mostly a rewrite port yes...15:04
Laneyget him to release, package it with the same packaging and rename the packages15:04
Laneyassuming it works etc15:05
sil2100Slowly slowly unblocking stacks...15:25
sil2100seb128: still around ;) ?15:47
Laneyrun15:48
Laneyrun fast!15:48
sil2100seb128: could you ACK the diffs? I want to publish the apps stack, here are the diffs:15:49
sil2100http://10.97.0.1:8080/view/cu2d/view/Head/view/Apps/job/cu2d-apps-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_gallery-app_0.0.67daily13.06.14.1-0ubuntu1.diff15:49
sil2100http://10.97.0.1:8080/view/cu2d/view/Head/view/Apps/job/cu2d-apps-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_notes-app_1.4daily13.06.14-0ubuntu1.diff15:49
sil2100robru__: ping16:00
sil2100kenvandine: ping!16:07
sil2100kenvandine: https://code.launchpad.net/~sil2100/cupstream2distro-config/remove_powerd_from_packages/+merge/16947916:07
sil2100kenvandine: could you check that? Since the platform stack does not work right now ;)16:08
sil2100hmmm16:11
kenvandinesil2100, done16:12
seb128sil2100, hey, I'm back, still need me16:17
seb128?16:17
qenghochrisccoulson: I think I'm hitting that same ARM instuction-set problem you discovered in December. What did you do to toolchains then?16:23
qenghoI'm curious if it regressed.16:23
chrisccoulsonqengho, the binutils update was never published (it's waiting on chromium). are you using the one from https://launchpad.net/~canonical-arm-dev/+archive/ppa ?16:24
sil2100seb128: yes ;)16:25
sil2100seb128: could you check those diffs and ACK?16:25
sil2100I'll publish that stack then16:25
sil2100kenvandine: thanks!16:26
qenghochrisccoulson: er, hrm. I'm using only stock precise. Did we just change chromium build-flags or -deps?  I don't remember reverting anything here, but I'll check.16:26
sil2100kenvandine: do I have to redeploy the stack for those changes to take effect?16:26
chrisccoulsonqengho, i suspect it will work if you use the updated binutils, assuming it's the same issue16:27
kenvandinesil2100, dunno16:28
seb128sil2100, those diffs look fine to me16:28
sil2100seb128: thanks!16:28
qenghochrisccoulson: but I can't rely on that when I give #security source packages, right?16:28
chrisccoulsonqengho, yes. it was always the intention to build with the fixed binutils, and publish that to the security pocket16:29
qenghochrisccoulson: FWIW: http://pastebin.ubuntu.com/5765160/  SEGV coming up, and a branch into middle of a function is queer.16:29
sil2100kenvandine: hm, maybe I'll redeploy the stack - it shouldn't hurt, right?16:33
sil2100kenvandine: yes, it seems that redeployment of the stack was needed ;)16:44
sil2100kenvandine: ping again ;p16:48
sil2100kenvandine: it seems the list of packages we added yesterday is not enough...16:49
sil2100kenvandine: https://code.launchpad.net/~sil2100/cupstream2distro-config/platform_add_extra_packages/+merge/16949616:49
sil2100robru__: poke me once you're here16:50
Laneyyay, found the right place to poke db5.3 to get it to build16:58
seb128Laney, great16:58
* Laney smacks the toolchain16:58
sil2100cyphermox: hi! Maybe you could approve? ^16:59
cyphermoxsure16:59
sil2100Thanks!17:00
cyphermoxdone17:02
* cyphermox goes to grab lunch17:02
sil2100\o/17:02
sil2100seb128: !17:13
sil2100seb128: can you help me with another stack?17:13
sil2100seb128: the platform stack, it has 3 diffs, there are 2 new packages (will need NEWing)17:14
sil2100seb128: could you:17:14
sil2100seb128: 1) ACK the diffs that are here http://10.97.0.1:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/17:14
sil2100seb128: 2) if they're ok, could you prepare lilly for the 2 new packages: dbus-cpp and location-service?17:15
sil2100seb128: I would then publish and those two would appear in the NEW queue17:15
seb128sil2100, is that the packages didrocks prereviewed for NEW yesterday?17:15
sil2100seb128: yes ;)17:16
seb128sil2100, diffs look fine17:16
sil2100seb128: we just disabled the powerpc unit tests for dbus-cpp packaging-wise, since fixing them would take a while (will fix them later)17:16
sil2100seb128: could you prepare things for publishing so that those can get accepted to the  queue?17:17
seb128sil2100, I don't know how to do that, let me have a look17:17
seb128sil2100, what I did earlier was just to pull the new stack config17:17
sil2100seb128: I think it's the part to upload things to lilly?17:17
seb128stacks/head/platform.cfg:    dbus-cpp:17:18
seb128stacks/head/platform.cfg:    location-service:17:18
seb128sil2100, I think that should be fine, they are already in the stack config17:18
sil2100location-service is there as well? Ok, since we had those, but we had them on daily_release: False17:18
seb128sil2100, let's try, if that doesn't work we will fix it on monday17:19
sil2100seb128: then I'm publishing, if they pop up in the queue, I would be grateful for NEWing ;)17:19
seb128will do17:19
sil2100seb128: and now I need to pop out, so see you later and thanks!17:19
seb128sil2100, it's a good time to call it a week17:19
seb128sil2100, have a nice w.e!17:19
=== seb128_ is now known as seb128
robru__sil2100, hi17:57
=== robru__ is now known as robru
robrusil2100, actually I'm running out for breakfast in a minute, apologies for my tardiness. Just email me whatever you were concerned about and I'll take care of it when I get back.18:03
Laneymlankhorst: do you ever get into a situation where someone overtakes you and then you end up riding uncomfortably fast to keep up with them?18:04
Eggman2013I have installed ubuntu from a netinstall19:16
Eggman2013it shows ubuntu base19:16
Eggman2013i only have the console.  Does anyone know how I get kde or gnome up and running?19:17
sarnoldEggman2013: try "apt-get install kde-full" as a starting point19:29
Eggman2013ok thanks19:29
sil2100robru: hi!19:46
sil2100robru: I wanted to poke you about the webapps stack19:47
sil2100robru: since the webapps-linkedin is failing to build due to a test failing19:47
sil2100robru: could you take care of that? I need to weekend now ;)19:47
sil2100robru: so see you around!19:47
=== m_conley is now known as m_conley_away
mlankhorstLaney: where? on a bike?20:21
mlankhorston a bike is simple, I just let them take all the wind and go fast myself :D20:22
Laneymlankhorst: yeah21:02
Laneywhen I feel like it's someone I should be faster than, yet somehow am not21:03
LaneyI did it today up this steep hill and almost died21:03
Laneyovertook him at the end though \o/21:03
mlankhorsthehehehe21:06
mlankhorstLaney: I did that a few days ago with 4 bikers all dressed up for it and with real bikes21:06
mlankhorstbut I was taking it easy at the calm, and the wind was against me, so I just let them carry me most of the time21:06
mlankhorst(me with a normal looking bike, with stuff in my bike bags, when they slowed down i took over and carried them for a bit, was fun, but it left me totally dead at the stables I was heading to)21:07
mlankhorstLaney: best way to do it is if you only go at 50-60% of your max capacity before yourself21:15
Laneywell that's what i thought happened at first21:16
mlankhorstyou definitely didn't, then :D21:16
Laneyhe sped off past me when i was slowing down for some lights so i thought i'd be able to catch up with ease21:16
Laneybut then it wasn't so easy21:16
mlankhorstsome people have trained a lot more than you21:17
Laneydidn't look like a serious biker21:17
mlankhorstanother time I just followed a single biker in his trail, talked to him a bit, he was just taking it easy while I was definitely at 80%21:17
mlankhorst(turns out a few days ago he did 100+ km in a group of 16 with 34km/h average, forgot exact distance)21:18
Laneymy god21:19

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!