[02:17] <TheMuso> p/c
[05:14] <pitti> Good morning
[06:51] <jibel> good morning
[06:54] <didrocks> Mirv: thanks for the doc update, good idea :)
[06:54] <didrocks> jibel: salut, ça va?
[06:55] <didrocks> Mirv: do you want a final review on dbus-cpp and if good, we enable it?
[06:55] <jibel> salut didrocks , ça va pas trop mal et toi?
[06:55] <didrocks> jibel: ça va bien, le temps reste sympa :)
[06:55] <didrocks> jibel: the flipped-container model will help us on the otto side I guess, but I need to talk with ogra to steal all available infos
[06:57] <jibel> didrocks, yes, but the nexus7 doesn't work yet
[06:57] <didrocks> jibel: right, I'll try to flash the N4 today
[06:58] <jibel> didrocks, sorry I can't help, I just have a 7
[07:00] <Mirv> didrocks: yes, please. debian/copyright could have 2012-2013 instead of 2013, but otherwise ready
[07:00] <didrocks> no worry! I just need to understand how those containers layers are working on the new model
[07:01] <didrocks> Mirv: well, TBH, in 2014, this will be outdated :p
[07:02] <didrocks> Mirv: do you think dbus-cpp-dev-examples should dep on dbus-cpp-dev? (as it's examples to use the -dev?)
[07:04] <Mirv> didrocks: I don't think they need the headers as they've already compiled (against dbus, via the headers)
[07:07] <Mirv> surely I can run the examples without the headers package installed, but maybe a Suggests would be in order
[07:08] <didrocks> Mirv: it's just a nitpick, otherwise, the source looks good :)
[07:08] <didrocks> Mirv: just building, want to check something on the .pc file
[07:13] <didrocks> Mirv: everything is fine for me, you add it to a stack (if not already) and we can try relaunching that component on that stack so that I can NEW it then?
[07:14] <Mirv> didrocks: ok
[07:14] <Mirv> adding/checking
[07:14] <didrocks> ok, ping me once done ;)
[07:28] <sil2100> Mirv, didrocks: it's added already, but daily_release: False right now
[07:31] <didrocks> sil2100: Mirv: so one of you get that to trunk and then deploy + relaunch?
[07:31] <didrocks> sil2100: Mirv: I'll pull it in the archive admin server and then NEW it
[07:31] <sil2100> \o/
[07:31] <Mirv> https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/enable_daily_release_for_dbuscpp/+merge/169113
[07:32] <sil2100> I'll browse through the stacks in the meantime
[07:32] <didrocks> ok, I'll let you run that, just tell me once it's gating the archive :)
[07:39] <sil2100> didrocks: as for the stacks that need manual publishing - we're still having a failure with the HUD stack (checking the progress with that in a moment), but so far the media stack looks ok for publishing
[07:39] <sil2100> didrocks: the packaging changes are sane and no breakage regarding HUD
[07:39] <sil2100> didrocks: as for the apps stack...
[07:39] <didrocks> sil2100: I trust you, just ping me if there are packaging change to review, otherwise, publish! :)
[07:40] <sil2100> didrocks: here the packaging changes have something strange in it ;p
[07:40] <sil2100> didrocks: one package has a dependency listed 2 times!
[07:40] <sil2100> http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/Apps/job/cu2d-apps-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_share-app_0.12~daily13.06.13-0ubuntu1.diff
[07:40] <sil2100> Minor thing, but still ;p
[07:40] <sil2100> qtdeclarative5-accounts-plugin
[07:41] <didrocks> sil2100: nice to clean in the future :)
[07:41] <sil2100> didrocks: but besides that it looks ok
[07:41] <sil2100> didrocks: could you just quickly re-review packaging diffs for media and apps? I'll publish them right away afterwards ;)
[07:41] <didrocks> sure
[07:42] <seb128> good morning desktopers
[07:42] <seb128> hey didrocks sil2100
[07:42] <sil2100> seb128: morning!
[07:44] <didrocks> salut seb128!
[07:44] <seb128> didrocks, lut ;-)
[07:48] <didrocks> sil2100: all good, +1 from me on both
[07:54] <sil2100> didrocks: webcreds looks more or less correct as well, publishing once you ack!
[07:54] <sil2100> didrocks: http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/WebCreds/job/cu2d-webcred-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_account-plugins_0.11daily13.06.13-0ubuntu1.diff
[07:54] <sil2100> (for quick access ;p)
[07:55] <didrocks> thanks sil2100 for sparing my clicks in browser :)
[07:56] <didrocks> sil2100: +1
[07:56] <Mirv> sil2100: relaunching platform to check dbus-cpp
[07:56] <sil2100> Mirv: did you redeploy?
[07:57] <Mirv> sil2100: not yet :)
[07:57] <sil2100> Mirv: ok ;)
[07:57] <sil2100> \o/
[08:00] <Laney> hey
[08:03] <seb128> Laney, hello
[08:04] <Laney> seb128: wie gehts?
[08:05] <seb128> gut, danke! und dir?
[08:05] <Laney> prima!
[08:05] <Laney> wondering why I started getting system compositor review emails though :P
[08:08] <seb128> the reason should be at the bottom of the email
[08:08] <Laney> yeah because I'm part of https://launchpad.net/~unity-system-compositor-team but it says the desktop team joined there in april
[08:08] <seb128> that seems about right
[08:08] <seb128> they maybe didn't do work until recently?
[08:09] <Laney> could be
[08:16] <Laney> jbicha: (yes I know you're not here but it seems you read the logs... get a bouncer :P) yes I can launch gedit, not that doing it from a terminal is something I tested. why?
[08:59] <seb128> pitti, hey, I commented back on the sessioninstaller merge request, not sure why but it doesn't catch on specific exceptions
[09:00] <pitti> seb128: did you perhaps try "except ParsingError"?
[09:00] <pitti> seb128: bonjour
[09:01] <seb128> pitti, I tried both "except ParsingError:" and "except DesktopEntry.ParsingError:" ... I'm sure I overlook something trivial there
[09:02] <pitti> seb128: could you try
[09:02] <pitti> except Exception, e:
[09:02] <pitti>     print('XXXX', type(e))
[09:02] <pitti> that should give you the actual type name
[09:02] <pitti> sorry
[09:02] <pitti> except Exception as e:
[09:03] <seb128> oh
[09:03] <seb128> <class 'xdg.Exceptions.ParsingError'>
[09:10] <seb128> pitti, I don't get it, if I try to print the exception it doesn't work
[09:10] <Mirv> didrocks: redeployed, reran, dbus-cpp built for armhf/i386/amd64 (powerpc failed)
[09:11] <seb128> pitti, like if I
[09:11] <seb128> except Exception as e:
[09:11] <seb128>     print(e.strerror)
[09:11] <didrocks> Mirv: is it a racy tests? maybe we can have tvoss having a look
[09:11] <seb128> pitti, it seems to hang
[09:11] <pitti> seb128: strerror? does that work? I've never seen that
[09:12] <seb128> pitti, it's from http://docs.python.org/2/tutorial/errors.html
[09:12] <pitti> seb128: ah, so you need to "import xdg", or "from xdg.Exceptions import ParsingError"?
[09:12] <seb128> except IOError as e:
[09:12] <seb128>     print "I/O error({0}): {1}".format(e.errno, e.strerror)
[09:12] <tvoss> Mirv, looking
[09:12] <pitti> seb128: I really hate this form of import, it makes namespaces so unobvious :(
[09:12] <pitti> seb128: ah, that's for IOError only, presumably
[09:12] <pitti> i. e. things that have an errno
[09:13] <tvoss> Mirv, got a build log for me?
[09:13] <seb128> pitti, oh, ok
[09:13] <seb128> pitti, the file has a from xdg.DesktopEntry import DesktopEntry
[09:13] <Mirv> tvoss: https://launchpadlibrarian.net/142306208/buildlog_ubuntu-saucy-powerpc.dbus-cpp_0.0.1daily13.06.13-0ubuntu1_FAILEDTOBUILD.txt.gz
[09:14] <seb128> pitti, let me try the import xdg
[09:14] <Mirv> didrocks: maybe, dbus related
[09:14] <pitti> seb128: right, so perhaps add "from xdg.Exceptions import ParsingError"
[09:14] <pitti> to keep the same style
[09:15] <seb128> pitti, yeah, that works ... so not obvious, hate namespaces
[09:15] <seb128> pitti, danke ;-)
[09:16] <tvoss> Mirv, I'm not sure, the tests are run under dbus-test-runner, not sure if that comes up correctly
[09:17] <didrocks> Mirv: you can maybe retry the build directly in launchpad, just to see if it can be reproduced reliably
[09:17] <didrocks> Mirv: if it pass, you can then relaunch the stack with "foo", it will catch up on the status without any upload on the ppa again
[09:21] <Mirv> didrocks: ok
[09:22] <Mirv> tvoss: trying a rebuild now, let's see if happens every time
[09:40] <Mirv> didrocks: same result on a rebuild
[09:40] <Mirv> https://launchpadlibrarian.net/142308466/buildlog_ubuntu-saucy-powerpc.dbus-cpp_0.0.1daily13.06.13-0ubuntu1_FAILEDTOBUILD.txt.gz
[09:40] <didrocks> tvoss: ^
[09:41] <tvoss> didrocks, interesting. Why do we build for powerpc btw?
[09:41] <didrocks> tvoss: because it's part of the archs we support in saucy
[09:41] <didrocks> so arch: any builds saucy
[09:41] <tvoss> didrocks, ack
[09:42] <didrocks> tvoss: and don't start this discussion, I have strong opinions on "we should ditch powerpc" :p
[09:42] <tvoss> didrocks, okay, trying to setup a build environment that helps me to reproduce the issue
[09:43] <didrocks> (especially as Qt5 doesn't support it through V8, so most of QML which will be our main desktop story, won't run on it expect if we get v8 fixes)
[09:43] <didrocks> tvoss: tell us if we can help you
[09:43] <tvoss> didrocks, send me a powerpc machine
[09:43] <tvoss> didrocks, what's the rationale behind powerpc support?
[09:43] <didrocks> tvoss: on the way! :)
[09:43] <didrocks> tvoss: no strong idea, maybe infinity can help shed some light on it ^
[10:26] <sil2100> didrocks: didn't we disable powerpc support?
[10:29] <sil2100> Laney: ping
[10:29] <didrocks> sil2100: hum, I don't think so
[10:29] <sil2100> Laney: hmm, it seems that indicator-datetime started FTBFS since today
[10:29] <sil2100> Laney: would you be able to help?
[10:37] <pitti> seb128: I'll push the three previous sessioninstaller uploads to bzr and then do a new release with your fix
[10:37] <pitti> PEOPLE, RESPECT Vcs-Bzr!
[10:37] <seb128> pitti, danke
[10:38] <Laney> sil2100: maaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaybe
[10:43] <sil2100> Laney: since I have no idea who to ping ;D
[10:44] <sil2100> Laney: and I saw you do some commits to indicator-datetime trunk!
[10:45] <mlankhorst> didrocks: poke
[10:47] <Laney> sil2100: you mean the pthread thing?
[10:48] <Laney> sil2100: if yes, I fixed it
[10:49] <Laney> sil2100: see http://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries
[10:49] <Laney> MP incoming
[10:50] <didrocks> mlankhorst: pong
[10:50] <mlankhorst> any eta on unity yet?
[10:51] <mlankhorst> and is it still going to land together with xserver
[10:51] <didrocks> mlankhorst: so unity is in saucy as you could see on ubuntu-devel ML :)
[10:51] <didrocks> mlankhorst: so we can plan that, I would prefer to have the stack green first
[10:51] <didrocks> which is what sil2100 is heading to
[10:51] <didrocks> then, we can decide for the D-switch-day :)
[10:52] <mlankhorst> I know but it's getting painful that I have to maintain 3 xservers atm for 2 distros
[10:52] <mlankhorst> erm s/distros/releases/
[10:53] <didrocks> sil2100: any idea when we can start to have a green stack for unity?
[10:53] <didrocks> sil2100: then, we should land that with the new Xserver ^
[10:53] <didrocks> mlankhorst: who maintained the patch unity side already?
[10:54] <sil2100> didrocks: *sighs* currently for sure we need to have HUD and indicators fixed, since those two issues cause many test failures
[10:54] <didrocks> sil2100: can you keep mlankhorst updated?
[10:55] <sil2100> didrocks: that's why I would like to have some additional people assigned to hud, indicators and unity for that
[10:55] <sil2100> didrocks: ok
[10:55] <didrocks> thanks :)
[10:55] <Laney> sil2100: ok, there it is for you to review
[10:55] <sil2100> Laney: \o/
[10:55] <sil2100> Laney: awesome! Thanks :)
[11:00] <mlankhorst> if xserver doesn't bump abi I'll probably upload 1.15 soon after
[11:08] <sil2100> Mirv, didrocks: https://code.launchpad.net/~sil2100/cupstream2distro-config/enable_address-book-service/+merge/169165
[11:11] <didrocks> sil2100: approved! I'll let you deploy and run the stack
[11:11] <didrocks> sil2100: pulling on the archive admin side meanwhile
[11:11] <sil2100> didrocks: can I deploy without this merged yet? Just using my branch in the meantime?
[11:12] <didrocks> sil2100: that's fine if you are sure to be on tip of trunk :)
[11:12] <didrocks> (there is no other changes in this file anyway AFAIK)
[11:14] <sil2100> didrocks: redeploying!
[11:15] <didrocks> \o/
[11:17] <sil2100> didrocks: done!
[11:18] <didrocks> let's cross fingers
[11:18] <didrocks> and get that one in!
[11:38] <seb128> mlankhorst, one server at the time, please don't go for 1.15 before that get discussed/tested
[11:39] <seb128> mlankhorst, also, do we have ati and nvidia binary drivers for the new xserver abi in the ppa for testing?
[11:39] <seb128> sil2100, didrocks: what's the recommended way to get a SRU to raring of one of the daily landed components? just ping you to have a raring landing for that source?
[11:40] <mlankhorst> seb128: not fglrx yet, but that one's always late, nvidia should already support it
[11:40] <mlankhorst> iirc
[11:40] <seb128> mlankhorst, well, we can't talk about landing until we get all the drivers...
[11:40] <seb128> so that's to resolve first
[11:40] <mlankhorst> we do have beta drivers, but tseliot may know if they're out of beta already or not
[11:41] <didrocks> seb128: yeah, basically, they are all stuck in manual publishing mode, so we can land a stack if nothing is waiting meanwhile
[11:42] <mlankhorst> anyway the delta between 1.14 and 1.15 is small, and almost exclusively contains bugfixes we'd want to pick up anyway..
[11:42] <seb128> mlankhorst, ok, good
[11:42] <tseliot> mlankhorst: I don't think fglrx supports the new ABI though
[11:42] <tseliot> not even the beta
[11:43]  * tseliot is already having a hard time adding support for Linux 3.10 to the drivers...
[11:44] <mlankhorst> 1.14 has been out for ages..
[11:46] <mlankhorst> tseliot: http://support.amd.com/us/kbarticles/Pages/AMDCatalyst13-6LINBetaDriver.aspx
[11:46] <mlankhorst> it does..
[11:46] <mlankhorst> or at least claims it does
[11:48] <tseliot> mlankhorst: oh right that's the 13.6 version
[11:49] <mlankhorst> tseliot: could we get that in the ppa?
[11:49] <mlankhorst> (or in saucy)
[11:50] <tseliot> mlankhorst: not in saucy but I bet it's in edgers already. So maybe we can just copy it from there
[12:00] <mlankhorst> seb128: it should be fine
[12:17] <Riddell> hmm, libical transitions has found some packages that don't compile anyway in saucy, gnome-panel kmymoney openchange
[12:24] <mitya57> Riddell: I can look at gnome-panel, do you have a build log link?
[12:24] <Riddell> sec
[12:25] <Riddell> mitya57: http://starsky.19inch.net/~jr/tmp/gnome-panel_3.6.2-0ubuntu4_i386.build
[12:25] <Riddell> test-dbus-applet.c:187:1: error: implicit declaration of function â€˜unsetenvâ€™ [-Werror=implicit-function-declaration] PANEL_APPLET_OUT_PROCESS_FACTORY ("TestAppletFactory",
[12:26] <mitya57> thanks Riddell
[12:47] <sil2100> Mirv, didrocks: if anything, I'm fixing up location-service right now - fixing linitian errors and the FTBFS
[12:47] <sil2100> Adding multi-arch
[12:47] <sil2100> Almost done
[12:47] <didrocks> great!
[12:47] <didrocks> thanks
[12:48] <Mirv> sil2100: great!
[13:16] <Riddell> evolution-data-server build-depends on libqt5?  interesting
[13:22] <jbicha_> Laney: adding Icon=evolution to the EDS .desktop works here
[13:28] <seb128> Riddell, through the ubuntu online account
[13:28] <Riddell> ah
[13:31]  * Sweeshark sobs ...
[13:31] <Sweeshark> PPA buildd is still hanging with no space left on device ...
[13:32] <didrocks> Sweeshark: buy a disk dude and send that to the DC ;)
[13:33] <czajkowski> Sweeshark: always your ppa :)
[13:34] <Sweeshark> didrocks: I dont need to buy a disc. Actually, I had something like 3 spare disc in my house that all could easily handle that.
[13:34] <mlankhorst> you just had to break things didn't you!
[13:35] <Sweeshark> czajkowski: you are suggesting it just my ppa having bad manners and I should get a different one?
[13:35] <czajkowski> libre office is unique how about that :)
[13:36] <mitya57> Riddell: fixed gnome-panel uploaded
[13:36]  * mitya57 likes "-DGMENU_I_KNOW_THIS_IS_UNSTABLE" option
[13:37] <Sweeshark> mlankhorst: Interestingly the buildd doesnt fail after an "no space left on device" -- it just hangs. If I do that with enough buildds I could easily DOS the PPAs as a whole ...
[13:38] <mlankhorst> oh the power that you have as libreoffice maintainer
[13:39] <mlankhorst> I bet you see cute puppies on the street too, and think that out in the open anyone can kick them :P
[13:39] <mitya57> Sweeshark: looks like there is a regression in Launchpad and it doesn't kill hung builds
[13:39] <mitya57> I had the same trouble with llvm-toolchain-3.3 today
[13:41] <pitti> seb128: do you mind if I update gvfs to 1.17.2, or would you rather stay at 1.16 for saucy?
[13:41] <pitti> seb128: git master builds fine on saucy and all tests pass
[13:42] <pitti> this will also fix these unnerving "meta_journal_iterate: found short sized entry, possible journal corruption" warnings
[13:42] <seb128> pitti, update is fine, assuming you deal with the breakages if there is any due to the update
[13:42] <pitti> seb128: sure
[13:42] <seb128> pitti, oh, you get those as well?
[13:43] <seb128> why did that start in saucy?
[13:43] <pitti> seb128: I'm not sure really
[13:43] <pitti> I often call evince from vim (for LaTeX stuff), and I didn't have them before
[13:43] <seb128> that was not happening in raring afaik and gvfs didn't change, I was starting wonderif if my disk has issues
[13:43] <pitti> but now evince is destroying my whole vim buffer wiht these
[13:43] <seb128> same with gedit here
[13:43] <seb128> the only thing that change is glib, I hope it's not a bug in glib
[13:43] <pitti> seb128: https://git.gnome.org/browse/gvfs/commit/?id=eb62d9
[13:44] <seb128> k
[13:44] <seb128> pitti, thanks for doing the update!
[13:44] <pitti> I could also just backport this, but I just landed new gphoto:// automatic tests in trunk
[13:44] <seb128> updating is fine, gvfs is not on crazy refactoring an anything, and the mtp backend saw some nice improvements
[13:44] <pitti> yeah, I want these, too
[13:45] <pitti> and we have fairly good test coverage these days, so I'm not worried about updating
[13:45] <jbicha_> pitti: do you use the ubuntu-desktop ppa for saucy?
[13:46] <pitti> jbicha_: I don't ATM, no; should I?
[13:46] <jbicha_> pitti: I put gnome-session 3.8 there and it builds with journald but I guess that isn't your problem
[13:47] <pitti> jbicha_: we don't ship journald ATM
[13:47] <attente> sil2100, i pushed a workaround for u-g-m's tests
[13:47] <pitti> jbicha_: I'd actually like to just re-enable the systemd binaries, so that it's in the archive for playing around with; even installing it won't change anything in the boot sequence, so it's fairly harmless
[13:48] <attente> sil2100, don't really remember why gedit was launched differently for that particular test, but hopefully the reason is gone now
[13:49] <sil2100> attente: thanks!
[13:50] <jbicha_> Laney: you had a note in g-terminal's bzr branch that you couldn't run gedit from the terminal, I didn't think that was still a problem...
[13:50] <Laney> jbicha_: oh, yes, I kind of remember that it resolved itself but I forgot what fixed it
[13:50] <Laney> you can delete that
[13:50] <Laney> and re: the eds icon - feel free to ask upstream what he thinks of that
[13:52] <Laney> it'll mean it's blank for ubuntu by default though
[13:52] <Laney> so if possible I'd rather eds ships one
[13:53] <jbicha_> also I was looking at /usr/share/accounts/applications/evolution-data-server.application
[13:54] <jbicha_> and it has <translations>evolution-data-server-3.8</translations> is that correct?
[13:54] <Laney> don't know
[13:54] <Laney> I assume mardy knew what he was doing when he set it up
[13:55] <Laney> but didn't check what the translation domain is / how UOA handles that
[13:55] <jbicha_> it's autogenerated from the build
[13:55] <Laney> right
[13:55] <seb128> jbicha_, hey, I'm not sure your gnome-menus "restore prefix" upload from earlier today is right
[13:55] <Laney> so I guess I'm redirecting you to mardy for that
[13:56] <Laney> someone tell him to hang out in this channel ...
[13:56] <seb128> he's on #ubuntu-devel
[13:56] <seb128> and -touch
[13:56] <seb128> the poor guys get enough pings like that :p
[13:56] <kenvandine> indeed
[13:56] <Laney> heh
[13:56]  * seb128 just pinged him about qml issues
[13:56] <Laney> he loves feeling wanted
[13:57] <seb128> we would be screwed without him
[13:57] <jbicha_> seb128: does it break anything? for some reason I saw that XDG_MENU_PREFIX wasn't being set on a new saucy install so maybe that's the real issue
[13:57] <Laney> seb128: speaking of not hanging out in channels, there was a discussion in #-app-devel earlier that you might find useful
[13:57] <Laney> ;-)
[13:57] <Laney> http://irclogs.ubuntu.com/2013/06/13/#ubuntu-app-devel.html#t11:52
[13:58] <seb128> jbicha_, we use /etc/xdg/menus/applications.menu in Ubuntu, not gnome-applications.menu
[13:58] <seb128> jbicha_, if you rename the conffile you need maintscript code to migrate to the new name and clean the old one behind
[13:58] <kenvandine> seb128, do you want another channel to hang out int?
[13:58] <kenvandine> s/int/in
[13:59] <seb128> kenvandine, not sure :p
[13:59] <pitti> jbicha_: in case you don't know, with debian/pkgname.maintscripts this can now be done declaratively, see man dpkg-maintscript-helper
[14:01] <jbicha_> ok I'll look into that
[14:03] <Laney> doesn't that menu stuff come from debian?
[14:05] <jbicha_> yes but we were skipping one of Debian's patches
[14:06] <Laney> ah, well it should be harmless if we don't set the env var
[14:07] <Laney> unless it defaults to something else
[14:10] <seb128> Laney, I think 3.8 default to prefixing gnome-
[14:11] <seb128> https://git.gnome.org/browse/gnome-menus/commit/?id=b53758987b4d04bf9c869bfd02c0ec1d252638bf
[14:11] <seb128> "gnome-session now sets XDG_MENU_PREFIX by default"
[14:11] <seb128> shrug
[14:11] <seb128> jbicha_, did you test your change on saucy (e.g with gnome-session 3.6)?
[14:11] <seb128> or did you test with your custom 3.8 that sets XDG_MENU_PREFIX?
[14:12] <jbicha_> I tested with a brand new Ubuntu GNOME I installed yesterday without ppas
[14:16] <Laney> OK so it looks like we need some conffile moving then AFAICS
[14:18] <seb128> shrug
[14:18] <seb128> hate conffiles
[14:18] <seb128> https://git.gnome.org/browse/gnome-session/commit/?id=6d7c73177858c3aeb2e65553b30dc536d4f1667d
[14:18] <seb128> gsm_util_setenv ("XDG_MENU_PREFIX", "gnome-");
[14:18] <seb128> so they hardcode the "gnome-"
[14:19] <sil2100> didrocks, Mirv: https://code.launchpad.net/~sil2100/location-service/fix_ftbfs_and_others/+merge/169215
[14:21] <Laney> that's not in our version
[14:21] <Laney> but maybe that obsoletes the g-menus patch
[14:22] <seb128> Laney, right, that's in 3.8 that jbicha_ is working on
[14:22] <seb128> but seems like our gnome-menus ships a gnome-applications.menus
[14:22] <seb128> I wonder why, it was not supposed to
[14:22] <seb128> seems like we are sitting in the middle and it's working by luck because there was a merge error
[14:23] <seb128> but we are likely using the wrong applications.menu then
[14:24] <Laney> that's the upstream change pointed to by the first commit you linked
[14:24] <didrocks> sil2100: we shold maybe talk to tvoss about ruby-ronn, it's in universe and I don't think that functionality would justify migrating this to main
[14:25] <didrocks> sil2100: no issue for now, the destination is universe, but once we will promote touch to main…
[14:25] <Laney> haha, they dropped Debian menu support
[14:25]  * Laney wipes away a tear
[14:25] <jbicha_> is this right? http://paste.ubuntu.com/5761617/
[14:26] <Laney> look at debian/gnome-menus.maintscript
[14:27] <sil2100> didrocks: ok, better keep that on our radar...
[14:27] <jbicha_> oh that's not in the manpage but that looks nicer
[14:27] <Laney> p1tti mentioned that earlier ;-)
[14:29] <Laney> it's not in the dpkg-maintscript-helper manpage because it's done by dh_installdeb
[14:31] <tvoss> didrocks, happy to remove it
[14:33] <Laney> rickspencer3: man
[14:33] <Laney> I like your wheels
[14:33] <rickspencer3> hi Laney
[14:34] <tvoss> didrocks, do we have something in main for doing md -> manpage?
[14:34] <rickspencer3> :)
[14:34] <rickspencer3> Laney, it looks fancier than it is
[14:34] <Laney> that's the bike way!
[14:34] <rickspencer3> Laney, assuming you are referring to my sewing machine looking bicycle ;)
[14:35] <Laney> also it looks super clean
[14:35] <Laney> I am so lazy at doing that
[14:35] <rickspencer3> hehe
[14:37] <mitya57> tvoss: I think we don't even have that in universe — as Markdown is not designed for that
[14:37] <mitya57> tvoss: but you can use restructuredtext...
[14:38] <mitya57> ah, in universe we have pandoc
[14:39] <pitti> seb128: yay, mtp is working quite a bit nicer now
[14:39] <seb128> pitti, \o/
[14:40] <sil2100> didrocks: in the meantime, do the changes look ok? I could ask kenvandine and cyphermox to review that if you're busy ;)
[14:41] <kenvandine> seb128, what do you think.. should system-settings be SideStage or MainStage?
[14:41] <kenvandine> not sure that was defined in the design, but i would think SideStage
[14:41] <seb128> kenvandine, sidestage imho
[14:42] <kenvandine> agreed
[14:42] <kenvandine> we'll leave it that way until someone complains :)
[14:42] <seb128> do we have a device with working sidestage? ;-)
[14:42] <Laney> get mpt to confirm then nobody can complain :P
[14:42] <seb128> I never really played with that
[14:43] <mpt> kenvandine, seb128: I hadn't even thought about that until it came up in conversation yesterday. Side stage for now, until I adapt every screen's design for a tablet.
[14:44] <kenvandine> mpt, thanks
[14:44] <sil2100> kenvandine: do you have a moment for a review? ;)
[14:44] <kenvandine> mpt, the design definately looked like it was sidestage
[14:44] <kenvandine> sil2100, sure
[14:44] <kenvandine> seb128, i don't have one... :)
[14:44] <sil2100> kenvandine: https://code.launchpad.net/~sil2100/location-service/fix_ftbfs_and_others/+merge/169215
[14:45]  * kenvandine should lobby for a manta :)
[14:45] <sil2100> kenvandine: this branch does a fix for FTBFS, add multiarch and do fixes for packaging
[14:45]  * kenvandine looks
[14:45] <Laney> how come it doesn't work on grouper?
[14:46] <tvoss> pitti, got a phone?
[14:46] <kenvandine> Laney, it's treated like a phone
[14:46] <kenvandine> because of the size
[14:46] <Laney> yeah
[14:46] <Laney> will that be changed?
[14:46] <kenvandine> dunno... might be a question for tvoss :)
[14:47] <kenvandine> tvoss, do you know if there are any plans to enable the SideStage on grouper?
[14:47] <Laney> I was under the impression that it was simply a bug
[14:47] <tvoss> kenvandine, not sure, better ask ... Saviq
[14:47] <Laney> but then it's been that way for ages so perhaps that is wrong
[14:47] <kenvandine> Saviq, ^^
[14:47] <Laney> also I phablet-flashed this morning and got a brick out the other side
[14:47] <Laney> stupid saucy :P
[14:47] <kenvandine> yeah
[14:48] <kenvandine> saucy goes boom on grouper
[14:48] <kenvandine> :/
[14:48] <Laney> but that's known from reading ogra_'s email
[14:48] <Laney> so shouldn't phablet-flash not have done it?
[14:49] <sil2100> kenvandine: thanks :)
[14:49] <Saviq> kenvandine, tvoss that's a design question, more, but it feels like there's not enough space on grouper to do sideStage
[14:49] <Saviq> Laney, ^
[14:49] <kenvandine> Saviq, understand
[14:49] <ogra_> Laney, hey, my email doesnt refer to phablet-flash ...  serguiens' does though :)
[14:50] <kenvandine> but it might be nice to be able to enable it even though it would be small
[14:50] <Laney> ogra_: No, but it did say that saucy is known broken there
[14:50] <ogra_> i'm only doing the flipped images
[14:50] <kenvandine> just so we can test stuff
[14:50] <ogra_> Laney, yeah, both of us did
[14:50] <Laney> so I wonder why phablet-flash was switched to saucy for grouper :-)
[14:50] <kenvandine> Saviq, so maybe some config we can flip just for testing purposes... just a suggestion
[14:51] <Saviq> kenvandine, Laney Shell.qml:289
[14:51] <kenvandine> more of our people have grouper than manta
[14:51] <Laney> ack
[14:51] <kenvandine> cool
[14:51] <Saviq> kenvandine, just change it to true or otherwise make true
[14:51] <kenvandine> perfect
[14:51] <Laney> we all got given Neuxs 7s so it's good to be able to do taht
[14:51] <Laney> better flash back to raring first though ¬_¬
[14:52] <didrocks> sil2100: lp:~didrocks/location-service/fix_weak_dep
[14:52] <didrocks> sil2100: grab that branch
[14:52] <didrocks> and then approve it :)
[14:54] <didrocks> sil2100: add that to daily, run the stack and tell me so that I can approve :) (where is the other one btw? in NEW?)
[14:55] <sil2100> ACK ;)
[14:55]  * didrocks goes for some exercice
[14:56] <kenvandine> sil2100, yeah, after that is fixed it's ready for approval
[14:57] <sil2100> kenvandine: pushed!
[15:03] <sil2100> kenvandine: hmm, since didrocks is away, I have a problem with the indicator stack, maybe you can help?
[15:04] <sil2100> kenvandine: http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-2.1build/205/console
[15:04] <sil2100> kenvandine: I'm getting such an error in the 'build' job for indicators
[15:06] <sil2100> didrocks: ^ once you're back
[15:08] <sil2100> didrocks, kenvandine: once the location-service merge is in, could you approve? https://code.launchpad.net/~sil2100/cupstream2distro-config/enable_location_service/+merge/169230
[15:08] <sil2100> I'll redeploy the platform stack then
[15:09] <kenvandine> sil2100, will do
[15:10] <sil2100> kenvandine: thank you! :D
[15:11] <sil2100> Sorry for so many reviews/questions
[15:11] <sil2100> It's a busy time as always
[15:14] <kenvandine> no worries
[15:18] <sil2100> cyphermox: ping! Are you busy?
[15:19] <cyphermox> sil2100: how can I help?
[15:19] <sil2100> cyphermox: so, I had to re-build indicators, as we had some important changes in bamf and indicator-datetime
[15:20] <sil2100> cyphermox: but hm, something happened and the build job is failing with: IOError: [Errno 2] No such file or directory: 'indicator-datetime_12.10.3daily13.06.13-0ubuntu1.dsc'
[15:20] <sil2100> Which is completely abnormal
[15:20] <sil2100> cyphermox: could you take a look? Since didrocks is out for exercise
[15:23]  * Laney flashes back to android and then starts again
[15:28] <cyphermox> I was alreday looking into indicator-datetime
[15:29] <cyphermox> you know, the pthread error
[15:29] <cyphermox> sil2100: for this one, did you rerun the prepare job for indicator-datetime?
[15:30] <sil2100> cyphermox: yes, I re-ran the stack with the list of packages 'bamf indicator-datetime'
[15:30] <sil2100> cyphermox: it then became yellow for some reason (?) and the build job started failing
[15:30] <cyphermox> ok
[15:31] <cyphermox> well it seems to me like the directory was probably move aside or someting
[15:42] <sil2100> didrocks: give me a sign once you're back
[15:44] <seb128> kenvandine, dpm: got it to work: http://paste.ubuntu.com/5761814/
[15:44] <seb128> kenvandine, it's building the .mo and installing them during standard build, and there is a "make pot" to update the template
[15:44] <kenvandine> seb128, cool
[15:45]  * seb128 has translated system settings working
[15:45] <Laney> that was weird
[15:45] <Laney> I kept getting errors flashing back to android, but after changing USB cables everything worked flawlessly
[15:48] <kenvandine> sil2100, sorry, i missed that build failure link
[15:48] <kenvandine> weird error... it's like it thinks it prepared but it didn't?
[15:48] <kenvandine> maybe LP rejected the upload?
[15:51] <sil2100> hm, maybe? Not sure how I could check that
[16:01] <kenvandine> sil2100, not sure...
[16:01] <kenvandine> i guess maybe try another build?
[16:02] <kenvandine> perhaps it was a transient error... like the source wasn't published yet in the PPA?
[16:02] <kenvandine> sil2100, look at the PPA to see if that version is there
[16:02] <sil2100> kenvandine: well, it failed even starting the build, so hm - the build step uploads the files to the PPA
[16:02] <sil2100> kenvandine: and if the build step failed even that, then how am I to fix that?
[16:02] <kenvandine> oh... prepare doesn't?
[16:03] <sil2100> hmmm
[16:03] <kenvandine> i thought prepare did that
[16:03] <kenvandine> and build watched it build in the PPA
[16:03] <sil2100> Maybe?
[16:03] <sil2100> Ok, so I'll maybe re-run with rebuilding indicator-datetime
[16:04] <kenvandine> sil2100, what's the status of dee-qt packaging?
[16:04] <sil2100> kenvandine: it was fine from what didrocks and me checked, so it's ready for adding I guess?
[16:04] <kenvandine> didrocks mentioned that it wasn't ready for daily release yet and was pending some changes to the packaging
[16:05] <kenvandine> sil2100, ok
[16:05] <sil2100> kenvandine: once I'll get a final ACK from didrocks, I'll add it and publish
[16:05] <kenvandine> https://code.launchpad.net/~ken-vandine/cupstream2distro-config/move_dee/+merge/168723
[16:05] <sil2100> kenvandine: argh, the same issue again ;/
[16:05] <kenvandine> he said to check with you once it's finished
[16:05] <sil2100> After re-running
[16:05] <kenvandine> humm
[16:06] <sil2100> kenvandine: ok, but first! Could you review this? https://code.launchpad.net/~sil2100/cupstream2distro-config/enable_location_service/+merge/169230
[16:06] <sil2100> As it was supposed to be enabled once the merge gets in, and it's in!
[16:06] <sil2100> :D
[16:06] <kenvandine> already looking
[16:06] <kenvandine> i was waiting for that merge :)
[16:06] <kenvandine> thx
[16:07] <kenvandine> done
[16:07] <sil2100> :)
[16:08] <sil2100> kenvandine: let me approve your branch once the location-service one gets in
[16:08] <sil2100> Since they're both from platform ;p
[16:10] <kenvandine> sil2100, well didrocks said i should copy some tests over too
[16:10] <kenvandine> not sure which ones though
[16:10] <sil2100> Some tests?
[16:10] <kenvandine> for dee
[16:10] <kenvandine> i guess make the platform stack run some of the autopilot tests from unity
[16:10] <sil2100> Ah, hm
[16:10] <sil2100> Right
[16:11] <sil2100> Makes sense
[16:11] <kenvandine> sil2100, suggestions?
[16:11] <kenvandine> i don't know much about the unity stack
[16:11] <sil2100> kenvandine: I would have to look at the tests, give me a moment - I'll comment on the MR then
[16:11] <kenvandine> sil2100, thanks!
[16:11] <kenvandine> i need to run a quick errand and grab a sandwich... bbiab
[16:12] <sil2100> ACK :)
[16:14] <didrocks> sil2100: back
[16:14] <didrocks> (after backlogging)
[16:14] <sil2100> ;)
[16:14]  * sil2100 broke something in indicators jenkins ;p
[16:15] <didrocks> how dared you?
[16:15] <didrocks> dare*
[16:15] <didrocks> do you have a link?
[16:15] <didrocks> (to the past II)
[16:15] <sil2100> http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-2.1build/206/console
[16:16] <didrocks> interesting
[16:16] <didrocks> did someone ssh to the machine?
[16:16] <didrocks> sil2100: do you see the version in the ppa?
[16:17] <sil2100> didrocks: yes
[16:18] <sil2100> I mean, I see the version, but did not log into the machine
[16:18] <sil2100> Since I wouldn't know what to fix anyway
[16:18] <didrocks> sil2100: you see that the ppa had it uploaded, right?
[16:19] <didrocks> sil2100: did you first tried to fix the warning in the prepare job?
[16:19] <didrocks> sil2100: I think someone did a partial rebiuld and there was an upload meanwhile in the ppa
[16:19] <didrocks> turning the job to yellow
[16:19] <didrocks> and so, there was a .project file
[16:19] <didrocks> but no ppa preparation
[16:20] <sil2100> didrocks: well, when I fired the indicator job, the prepare job was not yellow
[16:20] <sil2100> At least I saw everything green besides build and check
[16:20] <didrocks> sil2100: even when built failed the first time?
[16:20] <sil2100> didrocks: the build failed today for the first time because of the FTBFS in datetime
[16:20] <sil2100> didrocks: and prepare was green then
[16:21] <didrocks> sil2100: ok, but then, when you first saw that error (in run 206), it was when the prepare went yellow?
[16:22] <sil2100> didrocks: after we got the fixes in, I fired the indicator stack with bamf and indicator-datetime only, and then the prepare job turned yellow and build job failed with this strange error
[16:22] <sil2100> didrocks: I later tried retriggering only the build and check jobs, but the same
[16:22] <didrocks> sil2100: yeah, this error is a side effect, I need to see why the .upload wasn't removed
[16:22] <didrocks> sil2100: but anyway, we need to reconcile indicator-dateimt
[16:22] <didrocks> datetime
[16:23] <sil2100> hmmm
[16:23] <didrocks> seems like Riddell doesn't look at Vcs-Bzr :/
[16:23] <didrocks> sil2100: https://launchpad.net/ubuntu/saucy/+source/indicator-datetime/12.10.3daily13.06.07-0ubuntu2
[16:23] <sil2100> Eeek!
[16:23] <didrocks> sil2100: see the prepare message, it doesn't lie :)
[16:23] <didrocks> sil2100: but I need to check why the .project file wasn't removed
[16:23] <didrocks> normally the job should just have turned yellow
[16:24] <didrocks> and being ignore in the build phase
[16:24] <sil2100> didrocks: right, sorry about that, since the build job was throwing such a strange error I thought that the root cause is somewhere else ;p
[16:25] <didrocks> sil2100: no worry, there is clearly a bug there, but it's a side effect. On the where to look: always start on top :)
[16:25] <didrocks> and trust the message of it, see if it's valid :)
[16:25] <sil2100> didrocks: in the meantime: I re-ran the phone stack, so address-book-service should be published (will check), and we got the location-service enabled in platform
[16:25] <didrocks> sil2100: ok, saw the bug in the template FYI
[16:25] <didrocks> rm -Rf indicator-datetime_* *_indicator-datetime_* indicator-datetime ubuntu/indicator-datetime || true
[16:26] <didrocks> we don't rm <project_name>.project
[16:26] <sil2100> didrocks: aargh
[16:26] <dpm> seb128, cool, I'm going to steal that ;)
[16:26] <sil2100> didrocks: address-book-service dep-waits on powerpc ;/
[16:26] <seb128> dpm, https://code.launchpad.net/~seb128/ubuntu-system-settings/translations/+merge/169249 for info
[16:26] <didrocks> sil2100: I don't see address-book-service in NEW?
[16:26] <sil2100> didrocks: so the build job is still oging
[16:26] <didrocks> ah ok :)
[16:26] <sil2100> Missing build dependencies: qtpim5-dev
[16:26] <sil2100> Should I skip for powerpc?
[16:26] <didrocks> hum
[16:27] <didrocks> let me see
[16:27] <didrocks> normally, it should skip it now
[16:27] <sil2100> http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/Phone/job/cu2d-phone-head-2.1build/55/console
[16:27] <didrocks> sil2100: wasn't there another component as well?
[16:27] <didrocks> thanks for the link
[16:27] <didrocks> one sec, let me first fix the template while I'm at it
[16:27] <didrocks> (for the other bug)
[16:27] <sil2100> didrocks: in phone there's just address-book-service, since phone-app is disabled
[16:27] <sil2100> OK :)
[16:27] <sil2100> phew, confusing, so many things going on...
[16:27] <didrocks> there was one from Mirv IIRC
[16:28] <didrocks> sil2100: ah, it was failing on powerpc, I think tvoss is looking at it
[16:28] <didrocks> (failing as build and really failing)
[16:29] <sil2100> didrocks: which one do you mean right now? As there's so many things
[16:30] <didrocks> sil2100: dbus-cpp
[16:30] <didrocks> sil2100: ok, bug fixed in cupstream2distro-config, it will only be solved once we redeploy the stacks though
[16:30] <didrocks> (it's in the jenkins template)
[16:30] <didrocks> ok, no phone build
[16:31] <sil2100> ACK
[16:31] <didrocks> ok, my fix to ignore should have worked though
[16:32] <sil2100> While it's still pending
[16:32] <sil2100> didrocks: what should I do to unblock the indicator stack now? Redeploy the indicator stack?
[16:33] <didrocks> sil2100: rather merging (or directly pushing to trunk maybe) the missing changelog entry
[16:33] <sil2100> Maybe like this... not to add to the confusion, I'll let you finish fixing things first, and then once I can redeploy/re-run something, just poke me and I do it ;)
[16:33] <didrocks> then rebuild with both
[16:33] <sil2100> Ok
[16:33] <didrocks> let me investigate on the phone stack now
[16:33] <sil2100> I'll merge that change in
[16:33] <didrocks> thanks :)
[16:33] <didrocks> this is the kind of "it should just work" case for phone :/
[16:36] <didrocks> argh
[16:36] <didrocks> address-book-service_0.1.0daily13.06.13-0ubuntu1.dsc: permission denied
[16:36] <didrocks> normal as it's created by root
[16:36] <didrocks> not easy to reproduce though
[16:37] <sil2100> ...;p
[16:38] <didrocks> hum
[16:38] <didrocks> $ ~/work/cupstream2distro/trunk/watch-ppa -s saucy -p ubuntu-unity/daily-build
[16:38] <didrocks> 2013-06-13 18:38:20,398 INFO Checking the status for address-book-service (0.1.0daily13.06.13-0ubuntu1)
[16:38] <didrocks> 2013-06-13 18:38:20,398 INFO current_package: address-book-service 0.1.0daily13.06.13-0ubuntu1
[16:38] <didrocks> 2013-06-13 18:38:20,627 INFO Source available in ppa
[16:38] <didrocks> 2013-06-13 18:38:25,990 INFO arch: i386, status: published
[16:38] <didrocks> 2013-06-13 18:38:25,990 INFO arch: amd64, status: published
[16:38] <didrocks> 2013-06-13 18:38:25,990 INFO arch: armhf, status: published
[16:38] <didrocks> see, it ignored powerpc ^
[16:38] <didrocks> don't tell I forgot to pull in production…
[16:39] <didrocks> arghhhhhh
[16:39] <didrocks> "I forgot to pull in production"
[16:39] <sil2100> Ouch
[16:39]  * sil2100 looks at didrocks in a bad way
[16:39] <sil2100> hoho
[16:39] <didrocks> sil2100: well, the bright side should be that my code was good :)
[16:39] <sil2100> No worries, good that it's noting more serious!
[16:39] <sil2100> *nothing
[16:39] <didrocks> killed the build job
[16:40] <didrocks> let me relaunch the stack
[16:40] <didrocks> sil2100: way better isn't it? http://<IP_ADDRESS>:8080/job/cu2d-phone-head-2.1build/56/console
[16:40] <didrocks> you can see that powerpc was ignored :p
[16:40] <didrocks> sil2100: you can manually publish phone
[16:41] <didrocks> and then I'll NEW it
[16:41] <sil2100> Doing!
[16:42] <sil2100> didrocks: publishing
[16:42] <didrocks> \o/
[16:47] <didrocks> sil2100: NEWed!
[16:47] <sil2100> didrocks: thanks!
[16:47] <sil2100> didrocks: preparing MR for indicator-datetime
[16:47] <didrocks> seb128: when sil2100 will ask you to new dbus-cpp (once the build failure is fixed on powerpc), you can ack it, I've reviewed it
[16:47] <didrocks> seb128: same for dee-qt
[16:47] <seb128> didrocks, ok, thanks
[16:48] <didrocks> thanks to you :)
[16:48] <sil2100> \o/ Thanks guys
[16:48] <sil2100> Merge for dee-qt is ready, but I'm preparing a list of tests
[16:48] <didrocks> yep :)
[16:48] <sil2100> didrocks: https://code.launchpad.net/~sil2100/indicator-datetime/include_direct_push/+merge/169255
[16:48] <didrocks> sil2100: location-service?
[16:48] <czajkowski> didrocks: seb128 kenvandine any changes to LP projects/ppas need doing before tomorrow ping me else you'll need to ping wgrant and stevenk or file answers from now on .
[16:48] <didrocks> I remember building it :)
[16:49] <czajkowski> I'm pinging your 3 as your groups tend to need some changes from time to time
[16:49] <didrocks> czajkowski: thanks for the head's up and good luck to your new endovers again :)
[16:49] <seb128> czajkowski, :-( thanks, sad to see you leave Canonical, have fun in what you are going to do next!
[16:49] <didrocks> sil2100: hum
[16:50] <czajkowski> I'll still be around to poke you all re bugs :) don't worry http://www.lczajkowski.com/2013/06/13/a-bite-of-something-new/
[16:50] <didrocks> sil2100: if I take your changelog from 12.10.3daily13.06.07-0ubuntu2, there is Laney change + Riddell's one
[16:50] <didrocks> sil2100: while the upload just have Riddell's one
[16:50] <sil2100> didrocks: yes, the changelog entry has to be exact?
[16:50] <sil2100> Since we already had something in ubuntu2
[16:50] <sil2100> UNRELEASED, but still
[16:50] <sil2100> Should I move that to ubuntu3 ?
[16:50] <didrocks> sil2100: yeah, so that when we upload a new version (the next daily), we can see that Laney didn't slack :p
[16:50] <didrocks> and what's new in
[16:51] <sil2100> Ah, ok ;)
[16:51] <didrocks> sil2100: right, should be ubuntu3
[16:51] <Laney> O_O
[16:51] <sil2100> Fixing
[16:51] <didrocks> Laney: it's all your fault! :-)
[16:51] <didrocks> (it's not, but hey, it's Friday for me ;))
[16:51] <didrocks> (and I just got a free shower on the bike, so I can complain :p)
[16:52] <davmor2> didrocks: no that's your fault you are the one on the bike ;)
[16:52] <sil2100> didrocks: should I cheat Laney's changelog entry date and time :D ?
[16:53] <Laney> haha
[16:53] <sil2100> didrocks: since the direct push has been done later than Laney's
[16:53] <didrocks> davmor2: but but! at least, it's creating good memory, I race with another bike under the rain (but he did that being classy, he had a tie :p)
[16:53] <didrocks> sil2100: no need to cheat on date and time, the daily bot will bump it anyway
[16:53] <sil2100> ACK ;)
[16:53] <didrocks> sil2100: at least, it will be realistic: only the new version will have Laney's patch
[16:53] <Laney> whatever is going on
[16:53] <didrocks> not -0ubuntu2
[16:54] <Laney> oh I see, a naughty archive upload
[16:54] <didrocks> Laney: yeah, and that's not uncharted4!
[16:54] <sil2100> didrocks: pushed!
[16:54] <davmor2> didrocks: that's smart not classy, Classy would be with a tails bowtie and tophat :D
[16:55] <didrocks> davmor2: ahah, "bow ties are cool"
[16:55] <didrocks> I heard :p
[16:56] <didrocks> sil2100: way better, approving!
[16:56] <sil2100> didrocks: since location-service is in platform already, hm, should I redeploy now so that it gets into the archive, or wait for reenabling dee-qt?
[16:56] <didrocks> sil2100: location-service is all ready? I don't remember ;)
[16:56]  * didrocks looks at his notes
[16:57] <sil2100> didrocks: it should be!
[16:57] <didrocks> yeah, it is
[16:57] <didrocks> sil2100: I don't care, it will just give seb128 an extra button to push tomorrow as it's already reviewed :)
[16:57] <sil2100> didrocks: I fixed the FTBFS and fixed up the few issues
[16:57] <didrocks> so no hurry
[16:57] <sil2100> Ok
[16:57] <seb128> oh, right, didrocks is calling it a week
[16:57] <didrocks> sil2100: if you add a stack to lp:cupstream2distro-config
[16:57] <sil2100> seb128: hope you won't mind!
[16:58] <didrocks> sil2100: remember to ask an archive admin to pull on the archive admin machine
[16:58] <seb128> sil2100, don't worry
[16:58] <sil2100> didrocks: ok, only when adding a new stack, yes? What about when adding a new project to a stack?
[16:58] <sil2100> Since the FAQ said to contact the archive admin anyway
[16:58] <didrocks> sil2100: sorry, I meant a new project to a stack :)
[16:58] <didrocks> that's the whitelist basically
[16:59] <didrocks> to tell what is fine to copy to the archive
[16:59] <sil2100> didrocks: ok
[17:00] <sil2100> didrocks: about dee-qt... since in the e-mail you said only that dee-qt you had to do a packaging change with Architecture, but nothing else
[17:00] <sil2100> didrocks: is there something else that needs fixing?
[17:00] <didrocks> sil2100: no, it was fine
[17:01] <didrocks> eventually multi-arched if not
[17:01] <sil2100> didrocks: ok, so I'll add a list of tests to add, and then get kenvandine's branch in
[17:02] <didrocks> perfect!
[17:02] <sil2100> And new it
[17:02] <sil2100> With seb128  ;p
[17:02] <didrocks> sil2100: if you don't have to list every packages from unity
[17:02] <didrocks> sil2100: I think you can add "unity" from the tests packages
[17:02] <didrocks> or no, everything should be there already
[17:02] <sil2100> didrocks: right, since indicators
[17:02] <sil2100> I mean
[17:03] <sil2100> Wait, no, scratch that
[17:03] <sil2100> ;p
[17:03] <didrocks> :)
[17:03]  * didrocks scratches
[17:03] <czajkowski> didrocks: almost friday.... almost
[17:16] <sil2100> kenvandine: ping!
[17:16] <sil2100> kenvandine: I commented on https://code.launchpad.net/~ken-vandine/cupstream2distro-config/move_dee/+merge/168723
[17:16] <sil2100> kenvandine: could you add at least those two test suites?
[17:16] <sil2100> That's not all of them, but that's a good start I guess?
[17:17] <sil2100> kenvandine: once those are done, I'll approve it, as dee-qt is ready now
[17:17] <kenvandine> sil2100, cool, thx
[17:17] <sil2100> kenvandine: do not redeploy the stack yet though, since we'll do it tomorrow maybe?
[17:18] <sil2100> Or hm, actually
[17:18] <sil2100> We need an archive admin anyway probably
[17:18] <sil2100> didrocks: btw. about telepathy-ofono, last from the list
[17:18] <didrocks> yep :)
[17:18] <sil2100> didrocks: the package should be safe now, it's building and such - can I enable it?
[17:18] <didrocks> so no need for .3.3, .3 has the patch
[17:18] <didrocks> right?
[17:18] <sil2100> didrocks: yep, the dep is fixed in trunk now
[17:19] <didrocks> sil2100: let me look at my notes, one sec :)
[17:19] <sil2100> didrocks: if all is ok, could you https://code.launchpad.net/~sil2100/cupstream2distro-config/move_ofono_to_head/+merge/167344 ?
[17:20] <kenvandine> sil2100, we don't need an archive admin, it isn't a new package
[17:20] <sil2100> This way we could have it in, maybe seb128 could NEW it tomorrow
[17:20] <kenvandine> right didrocks?
[17:20] <sil2100> kenvandine: ah, right, it was released already! Forgot
[17:20] <sil2100> ;)
[17:20] <kenvandine> yup
[17:20] <didrocks> kenvandine: yep :)
[17:20] <kenvandine> although we weren't daily releasing it before
[17:20] <kenvandine> didrocks, does that matter?
[17:20] <didrocks> kenvandine: you are talking about hat package btw?
[17:21] <kenvandine> dee-qt
[17:21] <didrocks> yeah, it's fine :)
[17:21] <kenvandine> ok
[17:21] <didrocks> kenvandine: well, you need the archive admin side for pulling the white list on the copy machine
[17:21] <kenvandine> yeah, that is what i realized after responding to sil2100 :)
[17:22] <didrocks> sorry, didn't backlog all the way around :)
[17:22] <sil2100> ;)
[17:22] <kenvandine> sil2100, so i can just add those tests by name in the stack config and it'll find them?
[17:22] <kenvandine> along with unity-autopilot
[17:22] <kenvandine> in testpackages
[17:24] <sil2100> kenvandine: yes, just those, and also packages: you need to add like in other stacks
[17:24] <sil2100> And extracheck!
[17:24] <sil2100> Reenabling that
[17:26] <sil2100> didrocks: so, is ofono safe to re-enable?
[17:26] <sil2100> didrocks: if yes, could you approve the MR I pointed out? Or I can ask kenvandine to take a look ;)
[17:27] <didrocks> sil2100: I'm building it :)
[17:27] <sil2100> didrocks: with that, I think we're done for today with 'packages' stuff, just redeploing and NEWing tomorrow
[17:28] <didrocks> sil2100: yeah, just need the powerpc dbus-cpp fix I guess to unblock the platform stack, you will track that,
[17:28] <sil2100> didrocks: uuuh, one more thing I see...
[17:29] <sil2100> didrocks: the merge to indicator-datetime doesn't want to get merged ;/
[17:29] <sil2100> https://jenkins.qa.ubuntu.com/job/indicator-datetime-saucy-amd64-ci/7/console
[17:29] <sil2100> Dep problem?
[17:29] <didrocks> sil2100: telepathy-ofono could use some multiarch in the future, but fine with me in the current state
[17:29] <didrocks> sil2100: oh, just arch to arch: any maybe?
[17:29] <didrocks> sil2100: maybe libical isn't published yet?
[17:30] <didrocks> sil2100: yeah, it's still in proposed:
[17:30] <didrocks> https://launchpad.net/ubuntu/+source/libical
[17:30]  * sil2100 sighs :<
[17:30] <sil2100> Then we're blocked with everything then
[17:30] <didrocks> yep :/
[17:30] <didrocks> sil2100: do we need indicator-datetime right away?
[17:30] <jbicha> jenkins doesn't build against -proposed?
[17:31] <didrocks> jbicha: not the upstream merger nor ppas
[17:31] <didrocks> (it's the upstream merger in that case)
[17:31] <sil2100> didrocks: not sure, but it's in indicators, we would have to disable it for now
[17:31] <jbicha> won't that cause problems for transitions?
[17:31] <sil2100> didrocks: or can we skip it somehow?
[17:31] <sil2100> Since right now there's a failed build in the PPA
[17:31] <didrocks> sil2100: yeah, you can remove the .project file in /var/lib/jenkins/work/cu2d/head/indicator for that component
[17:31] <didrocks> and rerun with "foo"
[17:31] <didrocks> it will only take bamf
[17:31] <kenvandine> sil2100,  for packages, since the only thing we are really testing there is dee i am just listing libdee-1.0-4
[17:31] <kenvandine> sil2100, right?
[17:32] <didrocks> sil2100: I directly pushed arch: any for telepathy-ofono
[17:33] <sil2100> didrocks: thanks! I'm removing the .project file now
[17:33] <didrocks> sil2100: did you check the deps of the network stack?
[17:33] <didrocks> only qa?
[17:34] <didrocks> sil2100: doesn't seem even to use autopilot
[17:34] <didrocks> sil2100: so no dep should be fine
[17:34] <jbicha> is there a good reason not to build against -proposed?
[17:34] <sil2100> didrocks: ah, right
[17:34] <didrocks> jbicha: -proposed is not always in an installable state
[17:34] <didrocks> jbicha: so can have transient issues
[17:35] <kenvandine> didrocks, that makes sense... but then we don't have a way to build daily releases that include transitions that are waiting in -proposed
[17:35]  * sil2100 removing the file
[17:35] <sil2100> didrocks: will I have to re-add that file manually later on?
[17:36] <didrocks> kenvandine: yeah, we need to assess advantage/risks, especially when things are not published right away
[17:36] <kenvandine> yeah
[17:36] <kenvandine> tricky
[17:36] <jbicha> but say libunity-webapps needs to be rebuilt against libpackagekit-glib2-16 for a PK transition; you'd have to do it manually
[17:36] <kenvandine> we had friends broken last week because of the eds transition
[17:36] <didrocks> kenvandine: indeed :)
[17:36] <didrocks> jbicha: yeah, that's how we did it until now
[17:37] <didrocks> jbicha: and backport the changelog to the vcs
[17:37] <kenvandine> couldn't merge the branch that fixed it because it depended on proposed
[17:37] <didrocks> kenvandine: this is different, this is for the upstream merger
[17:37] <didrocks> (but basically the same question ;))
[17:37] <sil2100> kenvandine: best to ask Didier about the package list, since in the past we had to list all needed components in that ;p Not sure if that's still valid
[17:38] <sil2100> didrocks: hmmm
[17:38] <didrocks> sil2100: it's still valid, I have an idea to make is simpler, but need to show you guys and get what you think :)
[17:38] <sil2100> didrocks: I removed the .project file and re-run with foo, and indicators stack build failed ;p Do I need to redeploy it first?
[17:38] <didrocks> sil2100: did you push your commit for the dep on https://code.launchpad.net/~sil2100/cupstream2distro-config/move_ofono_to_head/+merge/167344?
[17:38] <didrocks> sil2100: ohoh, interesting!
[17:38] <didrocks> sil2100: no, that should be enough, let me have a look
[17:38] <sil2100> http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-2.1build/207/console
[17:39] <sil2100> That's new!
[17:39] <didrocks> sil2100: yeah, that's a bug in my code then :)
[17:39] <didrocks> hum
[17:39] <kenvandine> didrocks, can you look at the tests i added in https://code.launchpad.net/~ken-vandine/cupstream2distro-config/move_dee/+merge/168723
[17:39] <didrocks> why? I tested that though :p
[17:39]  * sil2100 thinks didrocks will be really happy tomorrow, since he's poked all the time
[17:40] <sil2100> :D
[17:40] <sil2100> Finally some peace!
[17:40] <didrocks> oh yeah!
[17:40] <didrocks> I'll more than appreciate that
[17:40] <didrocks> zen music :p
[17:40] <didrocks> I think I know what's wrong, one sec!
[17:40] <didrocks> sil2100: mind trying to relaunch?
[17:40] <sil2100> didrocks: foo?
[17:41] <didrocks> yep
[17:41] <didrocks> kenvandine: you should install all binary packages from the stacks + all the deps that are not installed by default
[17:42] <sil2100> didrocks: running \o/ Looks good so far
[17:42] <didrocks> (the rest is good)
[17:42] <didrocks> sil2100: phew! :)
[17:42] <sil2100> didrocks: and pushed the dependency removal to move_ofono_to_head
[17:42]  * didrocks fixes trunk now
[17:44] <kenvandine> didrocks, yeah but in this case none of the other binaries from the stack are tested yet
[17:44] <kenvandine> this is just to keep coverage of libdee
[17:44] <didrocks> kenvandine: yeah, but while we are at it, it's good to test them for instability, right?
[17:44] <kenvandine> i guess that is something :)
[17:44] <didrocks> kenvandine: and the day we're going to add tests, we just need to list those?
[17:44] <didrocks> kenvandine: not sure, just a thought :p
[17:45] <kenvandine> yeah, but adds overhead for each test run
[17:45] <didrocks> I hate this "list all packages", but it's a difficult thing to handle
[17:45] <didrocks> kenvandine: the install isn't a lot of time (it's 1 minute, we use eatmydata)
[17:45] <didrocks> so depends on you :)
[17:45] <didrocks> just know it's not costly
[17:47] <didrocks> sil2100: approved
[17:47] <sil2100> Awesomeful!
[17:48] <didrocks> kenvandine: the tests looks like a good selection to me, so depending on what you need to test, feel free to get it merged :)
[17:48] <kenvandine> i'm getting a package list now
[17:49] <didrocks> kenvandine: sil2100: nice progress on the NEW packages! let's keep it going :)
[17:49] <didrocks> I'll make some stats once all the daily_release: False are converted
[17:49] <sil2100> Thanks! Let's hope to have all the things pending done by tomorrow ;)
[17:49] <didrocks> that would be awesome!
[17:51] <kenvandine> sil2100, ok, i pushed my branch
[17:52] <kenvandine> can you approve it now?
[17:52] <sil2100> kenvandine: checking!
[17:52] <sil2100> kenvandine: hm, I think you'll have to re-merge trunk
[17:52] <sil2100> Or you did that already?
[17:53] <kenvandine> i did 20m ago..
[17:53] <didrocks> kenvandine: 20 minutes ago? that's stone age!
[17:53] <didrocks> :)
[17:53] <kenvandine> indeed
[17:53]  * kenvandine merges again
[17:53] <sil2100> Ah, ok, maybe the CI is old!
[17:54] <kenvandine> ok... merged and pushed
[17:54] <kenvandine> again :)
[17:55] <sil2100> Thanks!
[17:57] <sil2100> kenvandine: looks awesome
[17:57] <sil2100> GRRR
[17:57] <sil2100> kenvandine: approved
[17:58] <sil2100> But now BAMF fails to build
[17:58] <didrocks> ok, time to run for me I guess!
[17:58]  * didrocks waves good evening and good week-end
[17:58] <kenvandine> sil2100,  thx
[17:58] <kenvandine> didrocks, have a great weekend
[17:58] <sil2100> didrocks: bye! Thanks for everything and have a nice weekend!
[17:58] <didrocks> thanks kenvandine! have a nice day :)
[17:59] <didrocks> sil2100: you too, good luck for tomorrow, you are the first to wake up, you have the keys! :)
[18:07] <mfisch> can someone explain the difference between a g-properties-changed event and a g-signal where the signal is ProperyChanged?
[18:07] <mfisch> I'm getting the latter from ofono
[18:07] <mfisch> And I Assume that's just how ofono implemented it, as a signal rather than changing a real property?
[21:28] <jcastro> "
[21:28] <jcastro>     I am guessing Michael Terry is of French ancestry. I think Canadian, so quite possibly the name has to do with Deja-vu "already seen" and duplicity."
[21:28] <jcastro> mterry: are you Canadian?
[21:28] <jcastro> http://ubuntuforums.org/showthread.php?t=2154109
[21:28] <mterry> jcastro, :) no
[21:28] <mterry> jcastro, massachusetts man, born and raised
[21:29] <mterry> jcastro, funny thread
[21:29] <jcastro> indeed
[21:29] <jcastro> the Canadian thing had me chuckling
[21:30] <mterry> jcastro, I like the bit about his Celtic ancestry
[21:39] <Sweeshark> wow, that takes trolling other projects to a whole new level: rob weir triggers a special "send me a private mail so I can tell you how bad libreoffice is and why you should contribute to AOO" on the referer-URL ...
[21:40] <sarnold> haha
[22:21] <xnox> Sweeshark: where? =D
[22:29] <Sweeshark> xnox: seems to be removed again. it applied to the links coming from http://www.italovignoli.org/2013/06/some-food-for-thought/ ...
[22:29] <Sweeshark> xnox: screenshot are available upon request ;)


[15:10] <micahg> !dmb-ping
[15:10] <xnox> yo
[15:10] <cyphermox> o/
[15:10] <caribou> o/
[15:12] <cyphermox> I already pinged infinity elsewhere, since he's not in this channel
[15:14]  * micahg did as well
[15:14] <cpaelzer> fyi - stgraber is currently on a plane
[15:14] <micahg> thanks cpaelzer
[15:19] <cyphermox> bdmurray:  you around?
[15:31] <Laney> micahg: here, sorry
[15:34] <ogra_> cpaelzer, planes have wlan nowadays, that no excuse !
[15:34] <ogra_> *that's
[15:43] <xnox> !startmeeting Developer Membership Board
[15:43] <xnox> #startmeeting Developer Membership Board
[15:43] <meetingology> Meeting started Mon Jan 18 15:43:47 2016 UTC.  The chair is xnox. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:43] <meetingology> Available commands: action commands idea info link nick
[15:43] <xnox> aha
[15:44] <xnox> sergiusens, caribou are you about?
[15:44] <sergiusens> xnox, I am
[15:45] <caribou> me too
[15:45] <xnox> cool.
[15:45] <xnox> i believe we have a qurum, so let's start.
[15:46] <xnox> #topic PPU uploader Sergio Schvezov for snappy and snapcraft
[15:46] <xnox> https://wiki.ubuntu.com/SergioSchvezov
[15:46] <xnox> sergiusens, please introduce yourself and briefly elaborate on your application =)
[15:47] <sergiusens> Hi, I am part of the Ubuntu Core team at Canonical. I'm currently working on snappy Ubuntu Core, the snappy tool itself until recently (not directly now). Now I am leading snapcraft development and I would most of all like to be able to upload snapcraft.
[15:47] <sergiusens> I can elaborate if needed
[15:48]  * ogra_ is here to cheer for sergiusens :)
[15:48] <xnox> sergiusens, both are written in golang?
[15:48] <ogra_> *\o/*
[15:49] <ogra_> ^ (pompoms)
[15:49] <sergiusens> xnox, snappy in golang, snapcraft python3
[15:50] <ogra_> and while i totally trust sergios packaging skills, i really think the next step needs to be core-dev after this application :)
[15:50] <xnox> sergiusens, do you have continous testing for both against the archive? for example do you test building with golang 1.6 and python 3.5?
[15:50] <sergiusens> snapcraft, has 89% coverage of unit tests, 91% if you aggregate integration tests and running all our current examples. (the integration tests are also setup as autopackage tests, but I don't think we've ever uploaded that yet)
[15:50] <xnox> sergiusens, sounds good. yeah autopackage tests are the best to keep out broken toolchains from migrating (and breaking) your builds.
[15:50] <sergiusens> xnox, for snapcraft, we do test  with 3.5 in mind
[15:51] <sergiusens> xnox, for snappy we don't do 1.6 yet to support the gcc-go supported arches
[15:52] <sergiusens> xnox, snappy takes it one step further, each new PR (github, yes) triggers a test on image full run
[15:52] <sergiusens> test on image on one of the canonistack servers with ubuntu core
[15:53] <sergiusens> canonistack == internal cloud (just in case)
[15:53] <xnox> sergiusens, looking at the package names... is it really "snappy" the compresion algorithm package you are after to have upload rights for?
[15:53] <xnox> or is it ubuntu-snappy and snapcraft?
[15:54] <ogra_> the latter :)
[15:54] <sergiusens> xnox, oh, it is ubuntu-snappy; you are indeed right
[15:54] <ogra_> we dont use snappy in snappy
[15:54] <sergiusens> sorry about that :-/
[15:54]  * sergiusens fixed in the wiki
[15:55] <xnox> sergiusens, looking at the upload history i see that mostly mvo uploads ubuntu-snappy, have you ever uploaded ubuntu-snappy?
[15:55] <sergiusens> xnox, no, I just ask him
[15:56] <sergiusens> xnox, but mvo spreads thin these days, I thought I'd help him out since I know a lot about the ubuntu-snappy internals (and its packaging as I've worked on it through MRs/PRs)
[15:56] <xnox> but i do see that mvo endorses you.
[15:57] <xnox> !dmb-ping
[15:57] <xnox> do you have more questions for sergiusens ?
[15:57] <cyphermox> not me. I'm already familiar with sergiusens' work
[15:58] <Laney> yes
[15:58] <Laney> looking at https://launchpad.net/ubuntu/+source/ubuntu-snappy we can see that ubuntu-snappy is stuck in xenial-proposed
[15:58] <Laney> can you tell us how you'd find out what's going on there and maybe suggest how it might get unstuck?
[15:59] <sergiusens> Laney, I'd look at the excuses page
[15:59] <sergiusens> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[16:00] <sergiusens> what I see now after opening it, is that it seem the packaging has moved from 'any' to a subset of arches, so I'd need to talk to an archive admin
[16:01] <xnox> sergiusens, how do you check the current status of the autopkgtests for a package? for example for snapcraft?
[16:01] <sergiusens> if that is really what is wanted (but I'd have to check with the uploader who did that) :-)
[16:01] <Laney> does https://launchpadlibrarian.net/234022487/buildlog_ubuntu-xenial-s390x.ubuntu-snappy_1.7.2+20160113ubuntu1_BUILDING.txt.gz tell you anything?
[16:01] <sergiusens> xnox, I know there is a page for that too, I just don't have the link handy, sorry
[16:02] <xnox> sergiusens, on the excuses page above, do a Ctrl-F search for "autopkgtest for snapcraft" there are links to logs.
[16:02] <xnox> sergiusens, and it looks like it has always failed http://autopkgtest.ubuntu.com/packages/s/snapcraft/
[16:03] <sergiusens> xnox, yeah, that's why I said, the autopackage tests I worked on haven't been uploaded yet :-) This predates me
[16:04] <xnox> sergiusens, looking at ubuntu-snappy history for debian/ folder, last commit from you was in July 2015. Do you really need upload rights for ubuntu-snappy?
[16:04] <ogra_> to take load of mvo, yes
[16:04] <sergiusens> xnox, no I don't need them, I just really want snapcraft ones, ubuntu-snappy is a nice to have and to help my team mates
[16:06]  * Laney thinks it's okay for packaging to be stable
[16:06] <micahg> +1 :)
[16:07] <xnox> sergiusens, how do you choose a source packaging format for a package? and which one do you default to?
[16:07] <sergiusens> xnox, fwiw, September 2015 was my focus switch from ubuntu-snappy to snapcraft
[16:08] <sergiusens> xnox, I prefer to use non native (even though these packages say the contrary)
[16:08] <xnox> ok.
[16:09] <sergiusens> xnox, rule of thumb, native == ubuntu tools (or debian)
[16:09] <sergiusens> ubuntu exclusive
[16:10] <xnox> #vote grant sergiusens PPU rights for ubuntu-snappy, snapcraft
[16:10] <meetingology> Please vote on: grant sergiusens PPU rights for ubuntu-snappy, snapcraft
[16:10] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)
[16:10] <Laney> +1
[16:10] <meetingology> +1 received from Laney
[16:11] <Laney> crickets
[16:11] <xnox> #voters
[16:11] <meetingology> Current voters:
[16:11]  * xnox sigh
[16:11] <cyphermox> +1
[16:11] <meetingology> +1 received from cyphermox
[16:12] <xnox> +1
[16:12] <meetingology> +1 received from xnox
[16:12] <micahg> +1
[16:12] <meetingology> +1 received from micahg
[16:12] <xnox> that's it right?
[16:12] <xnox> #endvote
[16:12] <meetingology> Voting ended on: grant sergiusens PPU rights for ubuntu-snappy, snapcraft
[16:12] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[16:12] <meetingology> Motion carried
[16:12] <ogra_> \o/
[16:12] <sergiusens> yay, thanks
[16:12] <xnox> #voters Laney cyphermox xnox micahg
[16:12] <meetingology> Current voters: Laney cyphermox micahg xnox
[16:12] <caribou> congratulations sergiusens
[16:12] <sergiusens> caribou, thanks
[16:13] <xnox> #topic Core Dev Application - caribou
[16:13] <xnox> #url https://wiki.ubuntu.com/LouisBouchard/Core%20Dev%20Application
[16:13] <xnox> caribou, hello =) please introduce yourself
[16:13] <caribou> Hello, my name is Louis Bouchard,
[16:14] <caribou> my daily work revolves around fixing ubuntu bugs & doing SRU for the stable  releases
[16:14] <caribou> I also have upload rights for sosreport and makedumpfile since 09/14 if I remember right
[16:14] <caribou> since most of my work revolves around Main packages, I have decided to ask for core dev rights
[16:15] <caribou> I'm also trying to do more merges
[16:15] <caribou> and being more involved in the development process
[16:15] <caribou> finally, I do some development work around kdump-tools, makedumpfile & sosreport
[16:16] <Laney> if you get approved, will you help out with patch piloting? :)
[16:16] <caribou> I would like to.
[16:16] <caribou> I have a lot of colleagues who rely on sponsorship so I know the value of being available for review & upload
[16:17] <xnox> caribou, have you had SRUs that went south after publication? and what have you done to minimize damage?
[16:17] <caribou> xnox: luckily, none that I can remember
[16:18] <caribou> xnox: my first reaction would be to revert the change that causes failure if it can be easily identifie
[16:18] <caribou> d
[16:18] <xnox> caribou, are you aware of the crash report monitoring?
[16:19] <caribou> yes, very recently pitti pointed me to an issue with rsyslog that caused crashes
[16:19] <caribou> I also know that a lot of work on it is done by bdmurray especially on the retracers
[16:19] <xnox> right.
[16:19] <caribou> I've used apport-retrace myself a few times
[16:20] <xnox> caribou, and bdmurray can also set phasing on the updates, that is after update is published in -proposed it can be reset to 0% and thus prevent any new machines automatically installing or offering the update.
[16:20] <caribou> I also had a lot of exposure to kernel crash dumps but those are not treated as such
[16:21] <caribou> xnox: yes, I recently discovered about phased updates; a concept I had heard of from Google
[16:21] <xnox> caribou, yeah, we had it since 14.04 or so (not on release day, but later during 14.10/15.04 cycles phased updates for 14.04 were enabled)
[16:21] <xnox> !dmb-ping
[16:22] <xnox> any more questions for caribou ?
[16:22] <Laney> nope!
[16:23] <cyphermox> all good
[16:24] <xnox> micahg, ?
[16:24] <micahg> I'm good
[16:25] <xnox> #vote grant caribou ubuntu core dev rights
[16:25] <meetingology> Please vote on: grant caribou ubuntu core dev rights
[16:25] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)
[16:25] <xnox> +1
[16:25] <meetingology> +1 received from xnox
[16:25] <Laney> +1
[16:25] <meetingology> +1 received from Laney
[16:26] <Laney> micahg: cyphermox
[16:26] <cyphermox> +1
[16:26] <meetingology> +1 received from cyphermox
[16:26] <micahg> +1
[16:26] <meetingology> +1 received from micahg
[16:26] <Laney> |O|
[16:26] <cyphermox> sorry, I was in ppc64el lalaland
[16:27] <Laney> were you fixing udisks2?
[16:27] <Laney> yes you were
[16:27] <Laney> you great human
[16:27]  * xnox ponders what's the point of setting #voters if it doesn't end the vote
[16:27] <xnox> #endvote
[16:27] <meetingology> Voting ended on: grant caribou ubuntu core dev rights
[16:27] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[16:27] <meetingology> Motion carried
[16:27] <cyphermox> Laney: udisks2?
[16:27] <xnox> caribou, congrats =)
[16:27] <caribou> xnox: Laney: cyphermox: micahg: thank you very much !
[16:27] <Laney> http://autopkgtest.ubuntu.com/packages/u/udisks2/xenial/ppc64el/
[16:27] <cyphermox> caribou: congrats
[16:27] <Laney> dholbach: get this fine fellow on the patch pilot list!
[16:27] <caribou> happy to continue to be helpful to the community
[16:28] <mapreri> xnox: it restricts the ability to vote, otherwise everybody on the channel can cast a vote
[16:28] <xnox> mapreri, i see, thanks.
[16:28] <xnox> #topic next chair
[16:28] <xnox> who should be the next chair? is it Laney or somebody else?
[16:28] <Laney> infinity
[16:29] <cyphermox> yup
[16:29] <Laney> see the list on the agenda
[16:29] <xnox> #action infinity to chair the next DMB meeting
[16:29] <meetingology> ACTION: infinity to chair the next DMB meeting
[16:29] <Laney> take xnox and move to the end
[16:29] <Laney> when you are updating it
[16:29] <micahg> we need to kick off the nomination process for DMB soon
[16:29] <Laney> yes
[16:29] <xnox> #topic any other bussiness
[16:30] <micahg> current member terms expire 3/3 I think, so Feb 29 is the last meeting
[16:30] <xnox> do we really need to kick of DMB? i thought it's not soon.
[16:30] <Laney> 2016-03-10
[16:30] <micahg> sorry, 23/9
[16:30] <micahg> 3/9
[16:31] <xnox> so we have 3 people expiring right? bdmurray micahg and xnox ?
[16:31] <xnox> and infinity is on the other cycle, or on this cycle?
[16:31] <Laney> 2016-02-29 is the last meeting before
[16:32] <dholbach> Laney: thanks - will do
[16:32] <xnox> dholbach, oh you want to run our election? thank you =)
[16:32] <dholbach> what?
[16:32] <Laney> so we should start the 2 week vote on 2016-02-14
[16:32] <dholbach> sorry, I've only half been paying attention... I was referring to adding caribou to the pilots :)
[16:33] <xnox> dholbach, ah, haha, ok =)
[16:33] <Laney> therefore nominations starting on 2016-01-31
[16:33] <caribou> dholbach: Laney: I'll need some help if you want to get me going
[16:33] <Laney> although if it's anything like last time we'll have trouble finding people
[16:33] <Laney> so should maybe give it an extra week
[16:33] <xnox> Laney, sounds good. and i should draft a shout-out before that.
[16:33] <dholbach> caribou: sure
[16:33] <Laney> 2016-01-24
[16:34] <Laney> xnox: I'm thinking about retiring then too
[16:34] <Laney> will decde
[16:34] <Laney> +i
[16:34] <xnox> Laney, ahead of your current term?
[16:34] <Laney> yeah
[16:34] <xnox> Laney, i am legitimately expiring ;-)
[16:35] <xnox> Laney, last year you told me i should serve till the end of term, and not expire ;-)
[16:35] <xnox> Laney, you should stay for one more year.... =)
[16:35]  * Laney has been on DMB since 2011-02-22
[16:35] <Laney> we'll see, maybe nobody wants to nominate themselves anyway
[16:35] <xnox> fair enough.
[16:35] <xnox> anything else?
[16:36] <Laney> wait
[16:36] <Laney> will you start it with 3 + 2 weeks?
[16:36] <Laney> i.e. on sunday?
[16:36] <Laney> assuming you were volunteering to be returning officer
[16:37] <xnox> Laney, i think i am stuck with returning officer role. I was going to start it on monday the 25th, rather than sunday.
[16:37] <xnox> Laney, do we always end things on Sunday?
[16:37]  * xnox doesn't like working on sunday
[16:37] <Laney> usually advertise it as such anyway
[16:37] <Laney> at least before the meeting on the monday
[16:37] <Laney> it's more important for the actual vote
[16:37] <Laney> nominations not so much
[16:37] <xnox> ack.
[16:37] <xnox> i see, true.
[16:38] <Laney> so a week today?
[16:38] <xnox> yeap
[16:38] <Laney> ok
[16:38] <xnox> #endmeeting
[16:38] <meetingology> Meeting ended Mon Jan 18 16:38:20 2016 UTC.
[16:38] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-01-18-15.43.moin.txt
[16:40] <Laney>  thanks!
[16:40] <Laney> SPACE THANKS