[02:34] greeting sponsors! [02:35] Is anybody interested in uploading... [02:35] https://bugs.launchpad.net/ubuntu/+source/xubuntu-docs/+bug/1294932 [02:35] Launchpad bug 1294932 in xubuntu-docs (Ubuntu) "[needs-packaging] xubuntu-docs 14.04.1" [Undecided,Confirmed] [02:35] and... [02:35] https://bugs.launchpad.net/ubuntu/+source/shimmer-themes/+bug/1294459 [02:35] Launchpad bug 1294459 in shimmer-themes (Ubuntu) "[needs-packaging] shimmer-themes-1.7.2" [Undecided,Confirmed] [02:36] Please let me know if there are any questions or concerns === OutOfControl is now known as benonsoftware [06:16] Good morning [07:06] pitti, could you have a look at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.2.91/+build/5827268 [07:07] doko: yes, will do; thanks [07:08] thanks [07:24] good morning [07:31] that === tkamppeter_ is now known as tkamppeter [08:05] Laney: Can I kindly trouble you to remerge p11-kit to fix https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1027299 :) Alternatively, lmk if I should do it and seek sponsorship. [08:05] Launchpad bug 1027299 in p11-kit (Ubuntu) "Seperate out p11-kit-trust.so into a multiarch package to prevent errors in Wine" [Undecided,Confirmed] [08:33] RAOF: ah, I got umockdev-record --evemu working :) [08:34] RAOF: (mostly, need to fiddle with the "record device path" still) [08:41] @pilot in === udevbot changed the topic of #ubuntu-devel to: Trusty Beta 1 released! | Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> saucy | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: dholbach [08:41] * pitti hugs dholbach [08:41] * dholbach hugs pitti back :) [08:54] hey happyaron - how are you doing? did you see https://bugs.launchpad.net/indicator-keyboard/+bug/1290881? (just checking because I'm doing some sponsoring right now) [08:54] Launchpad bug 1290881 in indicator-keyboard (Ubuntu) "indicator-keyboard suppresses IBus candidate window" [High,In progress] [08:55] dholbach: haven't looked at the patch yet, will do it this night [08:55] happyaron, thanks a lot! [08:59] np, :) [09:00] dholbach, hey, happy piloting ;-) [09:02] mdeslaur, can you have a look at https://bugs.launchpad.net/ubuntu/trusty/+source/ca-certificates-java/+bug/1258286 ? [09:02] Launchpad bug 1258286 in ca-certificates-java (Ubuntu Trusty) "CAcert should not be trusted by default" [High,Confirmed] [09:13] * dholbach hugs seb128 [09:13] * seb128 hugs dholbach back [09:17] bluesabre, for bug 1294459 do you have a .orig.tar.gz file somewhere? [09:17] bug 1294459 in shimmer-themes (Ubuntu) "[needs-packaging] shimmer-themes-1.7.2" [Undecided,Confirmed] https://launchpad.net/bugs/1294459 [09:45] doko, good morning [09:45] doko, could you have a look here: https://code.launchpad.net/~robru/dbus-cpp/fix-ppc64el/+merge/211820 [09:45] ? [09:47] tvoss, you don't need the b-d on gcc-4-x, g++-4.x depends on it. please don't add an explicit b-d on g++-4.8, but use g++ instead [09:48] doko, ack [09:49] tvoss, maybe just define something like v_ext=4.7, and then use g++$(v_ext) [09:52] tvoss, ahh, and g++ is a dependency of build-essential, so you don't need it at all [09:52] doko, okay, so I should be good with just g++-4.7 for non ppc64el, correct? [09:53] yes [10:03] Hi all :-) [10:03] How are you doing? [10:05] doko, https://code.launchpad.net/~thomas-voss/dbus-cpp/fix-ppc64-el/+merge/211894 [10:07] tvoss, 4.8 still hardcoded [10:07] ifneq (,$(filter $(DEB_HOST_ARCH),ppc64el)) [10:07] v_ext = -4.7 [10:07] endif [10:07] export CC=$(DEB_HOST_GNU_TYPE)-gcc$(v_ext) [10:07] export CXX=$(DEB_HOST_GNU_TYPE)-g++$(v_ext) [10:08] tiny question: libdubsmenu & libdbusmenu-qt, in ubuntu 13.10 I can see only in the repos libdbusmenu-qt, before there was libdbusmenu-gtk2 and libdusmenud-gtk3 which required patched gtk2/gtk3 [10:08] are they now dropped and only libdubsmenu-qt is still there? [10:08] larsu: maybe you know ? :) :) [10:16] Mirv: hm, qtbase didn't get pushed back? === FourDollars_ is now known as FourDollars [10:30] doko, updated: https://code.launchpad.net/~thomas-voss/dbus-cpp/fix-ppc64-el/+merge/211894 [10:32] tvoss, ok. still b-d's on gcc-4.7, but doesn't hurt [10:33] doko, has to bd on gcc-4.7 until we update the papi to use > 4.7 [10:33] tvoss, g++-4.7 depends on gcc-4.7, so it is not needed ... [10:33] doko, sorry, got it now [10:38] damianatorrpm: "apt-cache search -n dbusmenu-gtk" still returns results on 14.04 for me [10:46] directhex: in case the email didn't make it, thanks! :) [10:47] Laney: it's not formally part of CI Train, so "the other CI" needs to merge it. trying that now. [11:08] dholbach: yeah, its in the branch: https://bazaar.launchpad.net/~smd-seandavis/xubuntu-artwork/shimmer-themes-1.7.2/files [11:08] ah ok, thanks [11:11] occasionally, there is some confusion with this package since its a multiple upstream tarball package, previous note with previous upload https://bugs.launchpad.net/ubuntu/+source/shimmer-themes/+bug/1227402/comments/7 [11:11] Launchpad bug 1227402 in shimmer-themes (Ubuntu) "Please update shimmer-themes to 1.6.2" [Undecided,Fix released] [11:11] thanks for taking a look :) [11:22] doko: sure, I'll take a look....it ftbfs? [11:24] doko: oh, nm, I see the test [11:34] mdeslaur, ok, thanks === MacSlow is now known as MacSlow|lunch [12:33] Laney: I see you are marked as janitor for ubuntustudio-live in the sponsors queue. Any more hinders in getting it through to universe? [12:34] zequence: I don't know what that means [12:34] Laney: From what I understand, it's uploaded, but needs approval from archive admins [12:34] All that means is that I made the last comment on the bug [12:34] Ah [12:35] It's been uploaded, yes, just waiting for approval [12:36] I have a habit of misreading things :P [12:41] doko: hi [12:42] I was wondering, about https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720545 [12:42] Debian bug 720545 in src:bash "bash: Please consider removing privmode.diff" [Important,Open] [13:13] why usb-creator is so buggy these days? === _salem is now known as salem_ === cmagina-away is now known as cmagina [13:43] in Kubuntu, what app is similar with Password and Encryption Keys for uploading GPG key? [13:46] Riddell: ^^ [13:48] Laney, stgraber: this should be a formality, but I filed it nevertheless: bug 1295133 [13:48] bug 1295133 in umockdev (Ubuntu) "FFE: record/replay of input devices using the evemu format" [Wishlist,New] https://launchpad.net/bugs/1295133 [13:48] already replying [13:49] Laney: wow, you're too fast :) [13:49] just happened to open the list :-) [13:51] Laney: yes, of course I'm reading incoming bugs, I watch the autopkgtest failures, and the Mir etc. guys know where I live :) [13:52] Got to say these things for completionism :P [13:53] pitti: ping, re LP: #1272359 [13:53] Launchpad bug 1272359 in aptdaemon (Ubuntu Trusty) "needs porting to Python 3.4" [High,In progress] https://launchpad.net/bugs/1272359 [13:53] barry: hey [13:53] pitti: hi [13:54] barry: I see similar failures like you, also with current 3.3 [13:54] pitti: there is no branch of aptdaemon that i can find that actually passes all its tests [13:54] barry: i. e. the "FAILED (failures=1, errors=2, skipped=4)" bits [13:54] barry: yes, that also happens in trunk [13:54] pitti: while d/rules runs the test suite at build time, it doesn't ftbfs because the test failures are ignored ;) [13:54] barry: I guess trusty around it changed enough to now make it fail [13:55] pitti: upstream test suite doesn't pass in any of 2.7, 3.3, or 3.4 [13:55] *nod* [13:55] pitti: i am very much inclined to simply disable the dep8 tests for now and file an upstream bug about the test suite [13:55] barry: back then when I filed it it still did (and only failed with 3.4), but apparently it now fails with current 3.3, too [13:55] pitti: 2.7 even ;) [13:55] barry: we can just retitle that bug [13:56] pitti: yep, i'll take care of that. do you have any objections to disabling dep8 for now? [13:56] barry: there's no aptdaemon stuck in -proposed due to it, so no need to disable this [13:56] barry: yes; that causes more technical liabilities, and the next upstream update might just silently get in with actual regressions [13:58] pitti: okay, i'm going to just fiddle with the bugs then and let upstream take it from here [13:58] barry: thanks [13:58] pitti: cheers [13:58] stgraber: hey looking at bug 1254120. trying to isolate problems with ifup/ifdown on bonds. do you know which part of ifupdown would be setting static ips (ip addr ...) ? [13:58] bug 1254120 in ifenslave (Ubuntu) "Bonded interfaces don't come down with a ifdown -a" [High,In progress] https://launchpad.net/bugs/1254120 [14:02] arges: looking [14:02] there isn't really "parts" in ifupdown, it's a gigantic source file :) [14:02] stgraber: yea, i noticed :) [14:03] but the commands comme from the .defn files which are parsed and expanded at build time [14:03] arges: so FWIW, I never expected my new package to fix bug 1254120 [14:03] bug 1254120 in ifenslave (Ubuntu) "Bonded interfaces don't come down with a ifdown -a" [High,In progress] https://launchpad.net/bugs/1254120 [14:03] stgraber: yea i've been trying to use strace and 'ifup -v' to figure out where the issues are [14:03] stgraber: figured as much, I looked at the change and didn't think it woudl either but tested it to make sure [14:04] i'll look through the .defn files. [14:04] arges: let me update my network testing box to see if I can reproduce that issue easily here [14:04] stgraber: yea, i'm doing this all in VMs and its pretty trivial to reproduce [14:05] my test box is physical hardware with LACP but that shouldn't matter in this case [14:06] yup [14:07] sladen: you still into fonts? [14:08] arges: I suspect something may be wrong somewhere in ifenslave which would explain why it's not obvious when running with -v but hopefully I can figure out what exactly once that box is done upgrading (I really should switch to something better than a single core 32bit Atom for that box :)) [14:08] sladen: fancy seeing if this tar is sane and can be built and works? starsky.19inch.net/~jr/tmp/oxygen-fonts-0.4.tar.xz [14:08] dholbach, I have to run, but re Bug 1294891 [14:08] bug 1294891 in Ubuntu "Ubuntu GNOME community wallpapers" [Undecided,Incomplete] https://launchpad.net/bugs/1294891 [14:08] we got permission from image authors to release work under cc-by-sa 3.0, so copyright file should be ok? [14:09] balloons: sergiusens: what can I help with to release calendar-app revision 205 or better? It's been blocking python2 removal for a while now. [14:11] stgraber: yea something intiially is causing it to not create the proper files in /run/network and the ifstate file isn't updated correctly, so I think ifup needs to work. The other question is, do we expect 'ifup bond0' to bring up slave interfaces or that needs to be done before bringing up the bond? [14:11] xnox, just push balloons around [14:12] balloons: i'm prepared to be a slave for you =) calendar-app, please please please =))))) [14:12] arges: ifup bond0 won't bring up slaves, it'll just sit and wait until slaves join. But slaves will bring up bond0, so "ifup eth0" should bring up eth0, bring up bond0 and then add eth0 to bond0 [14:13] stgraber: gotcha. [14:14] stgraber: so if i do 'ifup ' and the bond comes up, do we expect the ifstate file to have bond0=bond0 in it? [14:14] balloons: honestly changes from v201 to v205 are trivial, and are trivial to verify. We shouldn't need to wait on all the cool things to be developed and be ready. [14:15] arges: we do, though I suspect that may be the problem [14:15] lol xnox [14:16] stgraber i think so too [14:16] xnox, see my perhaps confusing mail on the list. We need to release calendar too. But trunk is broken. So I have a merge reverting the bad changes in trunk that we can land [14:16] alternatively, we could fix the trunk version of the app, then land the fixes for the test [14:16] balloons: do you want me to prepare v205 click, with diff of what changed is no code change. http://paste.ubuntu.com/7125444/ [14:16] balloons: you don't have to release trunk. [14:17] balloons: i'm asking to release revision 205. [14:17] balloons: which has _no code changes_ to the app. [14:17] balloons: merging back reverts is silly. It's a distributed version control system, checkout the revision you want to release, build the click for that revision # and upload to the store. [14:18] balloons: my changes were ready eon ages ago, why should i be blocked by broken trunk? i can trivially push current trunk to a staging branch and do push --override back to revision 205 if you wish. [14:19] balloons: then "release trunk" and push back the current trunk back in place. But it's silly if we need to do that. [14:19] balloons: am I missing something? [14:19] bzr branch lp:ubuntu-calendar-app -r205 is not broken, and is trunk. [14:20] https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1294181 [14:20] Launchpad bug 1294181 in Ubuntu Calendar App "Autopilot tests crashing in switch_to_tab helper" [Critical,Confirmed] [14:20] https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1294995 [14:20] Launchpad bug 1294995 in qtdeclarative-opensource-src (Ubuntu) "qmlscene crashed with SIGSEGV in value() when running calendar-app" [Undecided,Confirmed] [14:21] xnox, it sounds like we're going to go ahead with landing my mp which reverts the offending changes: https://code.launchpad.net/~nskaggs/ubuntu-calendar-app/revert-212/+merge/211813 [14:21] balloons: and? [14:22] balloons: dude, we need to fix packaging and metadata of the app. The app itself would be identical but the manifest revision number of where to fetch the tests from. [14:22] arges: hmm, nope, that's not it. In my setup here with eth0+eth1 in bond0 and bond0 in br1000, I get the expect behavior, proper bring down and consistent ifstate === MacSlow|lunch is now known as MacSlow [14:22] arges: now trying with IP config directly on bond0 as you have [14:22] balloons: with normal packages, i would have done direct to the archive upload weeks ago. [14:22] http://udisks.freedesktop.org/docs/latest/gdbus-org.freedesktop.UDisks2.Block.html#gdbus-method-org-freedesktop-UDisks2-Block.Format [14:23] seems like erase: '' no longer works on trusty [14:23] xnox, I'm blocked on releasing anything unless tests pass [14:23] and tests fail in trunk because the app has some critical bugs [14:24] regardless, it sounds like we are going to be able to land something today that should solve your issue [14:24] so details aren't important [14:24] arges: nope, things still get brought up correctly with "ifup eth0 && ifup eth1" and brought down correctly with "ifdown -a"... [14:25] now trying with an exact copy of your config :) [14:25] balloons: "I'm blocked on releasing anything unless tests pass" that sounds really odd, can you ellaborate where this requirement is comming from? because that should be blocking merging and landing new features, this should be blocking any other no-change rebuilds. E.g. just like we did for qt5.2 landing and etc?! [14:25] hmm [14:25] balloons: the details are important, as I have been blocked for about 4 weeks due to inability to do click uploads. [14:25] balloons: those that _do_ not match trunk. [14:26] stgraber: it works if the bond is using dhcp, but not with a static ip [14:29] stgraber: in fact it seems to affect any static interfaces... I just set eth1 to static and tried to ifdown it with no luck [14:30] Hey folks, I see (https://launchpad.net/builders) that ppc64el builders are available for official distro but not for PPAs. How can I provide ppc64el packages on a PPA? [14:31] roadmr: that's only possible with devirtualised PPAs, which are only provided for special purposes [14:32] arges: I don't use any dhcp here [14:33] arges: here are the config I tried so far: http://paste.ubuntu.com/7125505/ [14:33] arges: both come up fine with either "ifup eth0 && ifup eth1" or "ifup -a" and they get brought down cleanly with "ifdown -a" [14:34] stgraber: let me adjust my config here [14:37] cjwatson: devirtualized meaning native hardware? oh those must be scarce... who can help me decide if my purpose is special enough and maybe give us access to this? [14:37] Laney: do we have a codesearch set up on the ubuntu somewhere? [14:37] ask again, who takes care of usb-creator? [14:37] stgraber: i also found another issue where if I have a bond my vm takes much longer to boot up because i get 'bonding: bond0: unable to update mode because interface is up' [14:37] so i should file a separate bug for that [14:38] mdeslaur: ya: http://ubuntu-codesearch.surgut.co.uk/ [14:38] roadmr: #webops internal [14:38] be patient with it and refresh a couple of times if you get timeouts [14:38] xnox: ping [14:38] Laney: sweet, thanks! [14:38] cjwatson: great, thanks so much for the info. I'll ask there [14:38] maxiaojun: hey! [14:39] stgraber: i can still easily reproduce with http://paste.ubuntu.com/7125534/ [14:39] arges: so even if your config (dropping the eth0 and replacing eth1 by eth0 and eth2 by eth1), I still get things to work here... [14:39] if I change bond0 from static to dhcp it works [14:40] xnox: usb-creator's "Erase Disk" seems totally broken in trusty [14:40] maxiaojun: yeah. I have seen patches posted to the bugs on usb-creator. But I didn't review / upload them yet. I was planning to do it today or tomorrow. [14:41] stgraber: I'll try this on hardware. Mind reproducing this in a VM? (just to prove i'm not crazy) [14:42] arges: if I can find a machine where I have some kind of VM technology installed :) [14:42] (sorry, LXC maintainer here) [14:42] xnox: i cannot fix it even if i traced to usb-creator-helper [14:42] stgraber: ah. ok i'm testing on hw now [14:43] Laney: curious, is that just for the dev release? [14:43] jdstrand: ya [14:44] YokoZar: I uploaded that, thanks for pointing it out [14:44] mterry, how do I test on the phone? branch and compile? [14:44] Cimi, the wizard? [14:45] yup [14:45] Cimi, yeah you could do that, and run it manually... [14:45] ok [14:45] Cimi, alternatively, you could use the upstart job that we don't actually ship in the deb, but is in the source tree [14:45] Cimi, place that in /usr/share/upstart/sessions [14:46] stgraber: just to confirm you've been testing trusty right? [14:46] xnox: call to UDisks2's format either error or timeout (cannot find a way to do 'quick format' and do not where the time limit is set) [14:46] arges: yep, up to date trusty + ifupdown from my PPA [14:47] stgraber: ok i'm using the same in my vm with your ppa, and still reproducing it [14:48] xnox, so we are landing a fix to the store right now. As far as what happened, well when qt 5.2 landed the trunk and supposed stable version of calendar stopped working due to the bugs I linked. I understand you are upset because you made only manifest changes, however I cannot release an old revision, it has to be current trunk [14:49] arges: testing in a clean vm here now [14:49] stgraber: ok... on hardware. ifdown -a; ifconfig (bond0 is gone!), ifup -a && ifdown -a (bond0 is still there) [14:49] good, so I'm not insane :) [14:50] oh no [14:50] misread [14:50] balloons: that sounds very wrong that " we cannot release an old revision," [14:50] balloons: we do this all the time for all components in the archive, in main and the ubuntu-touch seeds, both click apps and .debs [14:50] balloons: we should fix that. [14:51] xnox, afaict releasing an old version would still have broken tests. So yes it would have fixed your issue, but not the issues with the landing team and wouldn't pass the store review [14:52] balloons: ?! dude didrocks himself uploads things to revert, or do no-change uploads without regressing beyond what was on the image already. [14:52] balloons: e.g. we go up and down broken versions all the time. [14:52] balloons: i'd love to hear comments from the landing team about this. [14:53] xnox: can you stop trolling and start helping in the bazillion of regressions we have please? [14:53] xnox, I have things rejected all the time for the store.. [14:54] anyways, your pain is not just your own.. the calendar devs, landing team, everyone has felt the impact of calendar regressing. But it's fixed now [14:54] xnox: and we do test the revert before uploading and ensuring we don't introduce regressions compared to latest promoted image FWIW [14:54] stgraber: on hw: reboot interfaces are correct, ifdown -a - everything is down, ifup -a - I get a kernel message 'bonding: bond0: unable to update mode because interface is up' and I noticed in ifenslave it tries to set the bonding mode but that command fails... [14:54] well, fixed in the sense you'll get a new build [14:55] didrocks: correct. and ballons seems to think that this is not the case here. [14:55] and on my vm, I get that kernel message right on boot every time (in fact it delays boot up by a minute or so) [14:56] didrocks: sure, what do you want me to fix in the fork of calendar-app form revison 201? [14:57] xnox: I'm not sure about anything right now, calendar-app has no issue with balloons's fixes from what I know of [14:57] didrocks: it appears to have been accepted to have a certain baseline from way before qt5.2 uploads et.al. [14:58] didrocks: gallery-app? [14:58] xnox: read #ubuntu-touch for the regressions [14:59] didrocks: dude calendar_app is 100% green with no crashes http://ci.ubuntu.com/smokeng/trusty/touch/mako/248:20140320:20140304/7277/calendar_app/ [14:59] xnox: I know that link [14:59] didrocks: please explain how calendar-app is not in a releasible state up to revision 205. [14:59] in case you wonder [14:59] I don't know [14:59] did I say that? [14:59] did I write that? [15:00] didrocks: no. But balloons above claims landing team is blocking releasing calendar-app. [15:00] xnox: so how do you want me to explain something I didn't write? [15:00] balloons: what's about this? ^ [15:00] didrocks: balloons: so what do I need to do to release 205? do you want to execute full manual testing plan? [15:01] didrocks: well, I'm trying to find out what needs doing to release calendar app to revision 205 =)))) but i don't know who would know =)))) [15:01] xnox, ?? What do you need. We are releasing a build from today that contains everything up through rev211, which has your changes [15:01] barry: big +1 on dropping 3.3 [15:01] just wait for it to land and you should be set? [15:01] xnox: yeah but please don't assume and start telling things that aren't written [15:01] xnox: there is enough pressure and confusion on the real regression [15:02] no need for noise on top of that [15:02] that would be appreciated [15:02] pitti: \o/ [15:02] balloons: what's special about today vs all the past 4 weeks. I mean fine, but what can I do to prevent 4week delays like this?! [15:02] barry: that's essentially "drop it from py3versions; rebuild $world; remove package", right? [15:03] didrocks: well i have spare cycles and time to test and release things, yet people who can release are over-worked with "the real regressions" [15:03] xnox: yeah, and not sure why you are telling that I wrote we are blocking you [15:03] pitti: yes, although $world only needs to include packages with extension modules (to be identified) [15:03] didrocks: i'm asking how to help. Can i have access to e.g. click packages releases? and be one more lander for that? [15:03] xnox: I don't know, I can't release click package either === qengho is now known as CardinalFang === CardinalFang is now known as qengho [15:04] didrocks: cause i've checked all the ci-train stuff, but the click/core-apps are not listed. Who owns those? [15:04] balloons: is it only you who can release core-app clicks? [15:04] pitti: doko is going to upload 3.4 final tomorrow or this weekend, so let's wait for that [15:04] barry: ack [15:04] xnox: and sergiusens [15:04] but you just started a mail on the ML [15:04] arges: just for fun, can you comment out eth0 in both your setups and try again? [15:04] if you want to discuss that on IRC, use IRC [15:04] don't double the discussion [15:05] arges: if that magically makes the issue disappear for you, that'd at least explain why I can't reproduce your problem [15:05] didrocks: well there is no resolution. i basically got told off, to sit and wait and do nothing it will be done "today". [15:05] stgraber: sure i'll try it [15:06] xnox: on the ML? You wrote the email 20 minutes ago and you already get one answer [15:08] stgraber: wierd... without the extra eth0 interface ifdown -a && ifup -a works fine [15:09] stgraber: i looped it about 10 times with no problems [15:09] stgraber: i'm going to have to write some additoinal tests for ifupdown : ) [15:09] arges: good, so that confirms what I'm seeing here. [15:09] arges: now the question is wth is eth0 triggering the bond somehow... [15:11] I guess diffing "ifup -a" with "ifup --exclude=eth0 -a" may point us in the righ direction [15:11] well, both of those with -v obviously [15:12] good idea. i'll give that a try [15:13] just ifup/ifdown of eth0 doesn't seem to do anything wrong, so it's pretty confusing === FJKong is now known as FJKong_afk [15:13] didrocks: no, i've emailed to the ML based on the conversations with balloons. After that, you, ballons and I continued talking about this topic. [15:14] xnox: ack then, seems it's resolved now though, right? balloons is going to release it? [15:14] stgraber: confirmed that ifdown -a && ifup -a --exclude=eth0 do the correct thing for 5 iterations [15:15] arges: hmm, I'm getting an error from lockfile when doing ifup -a, I wonder if that could be the problem [15:15] didrocks: this landing is resolved, yes. the backlog in .click releases of core-apps is subpar and needs more people helping out. [15:15] darkxst, if the content is all cc-by-sa - all the files should say so [15:15] sergiusens: balloons: can you train me up to prepare and help with releasing .click core-apps? [15:15] xnox, sure [15:16] xnox: yeah, that was on the schedule to discuss this week to have one release process for debs and clicks, but regressions blocked to take the time for it [15:16] not much training needed; I'll ping back later today [15:16] ah, right [15:16] we can do it then as well [15:16] sergiusens: balloons: that would be appreciated and hopefully would free you up your development time on more urgent things. [15:17] sergiusens: no time due to regression and not around tomorrow [15:18] stgraber: are you only seeing this with -v? [15:18] didrocks, I'm not around tomorrow either [15:18] xnox, do you have a device? [15:19] arges: that can be ignored, it was just the ntpdate hook being unhappy, I moved it away for now [15:19] mterry, it's not optimal, takes ages [15:20] balloons: i have grouper and mako. [15:21] arges: "ifup eth0 eth1 eth2" => missing bond0 in ifstate, "ifup eth1 eth2 eth0" => it's in there and everything works [15:21] didrocks: "that was on the schedule to discuss this week" where would this discussion be? [15:22] or did you mean last week / vUDS? [15:23] xnox: this week [15:23] didn't get room last wekk [15:23] week [15:23] stgraber: that's really wierd [15:23] just a hangout [15:23] xnox: you're welcome to organize it [15:23] and promote it [15:24] didrocks: i wouldn't know full current release process of either debs or clicks, and even less on how to apply common policies/current practice to both. [15:24] didrocks: so i'm not at all the right person to drive that session. [15:24] ok, so let's us driving it [15:25] when we'll get time for that [15:25] seb128, how you test on the phone? [15:25] seb128, it takes light years to compile [15:25] didrocks: i wish to be an ad-hoc lander and help releasing things, but so far that was not possible. [15:25] Cimi, light years is an unit of distance :p [15:26] Cimi, you can cross compile on your desktop [15:26] seb128, I know it is, but in my mind imples very far away with current speeds :) [15:26] if you have a build tree it's not that slow to run make [15:26] also often we work on qml [15:26] seb128, I ran debuild [15:26] on the phone [15:27] after fifteen years I run wizard/test.sh [15:27] and it aborts [15:27] fantastic :D [15:27] could not connect to display [15:29] yeah, you don't get to run things by hand on the phone [15:29] you need to --desktop_hint= if you do [15:29] but I never tried the wizard on the phone, maybe mterry did [15:29] seb128, Cimi: I did, using the upstart job [15:30] seb128, Cimi: but really, integration with phone setup is a TODO (ideally, it will be launched by greeter if needed) [15:30] mterry, how can I test sim card? [15:30] mterry, I did make install [15:30] Cimi, try using the upstart job [15:31] Cimi, install your built deb [15:31] how do I play with the upstart job? [15:31] then copy the upstart job from the source to /usr/share/upstart/sessions [15:31] then reboot [15:31] you copy it in the init dir (system or user) [15:31] reboot or just "start " [15:31] well, you might need to ack it for that [15:32] tweak the start conditions [15:33] mterry, job name? [15:34] Cimi, wizard/ubuntu-system-settings-wizard.conf [15:34] mterry: ~/.config/upstart is read by session upstart as well. [15:34] mterry, start ubuntu-system-settings-wizard doesn't work [15:35] Cimi, did you manually copy the job to the upstart directory? [15:35] mterry, /usr/share/upstart/sessions [15:36] Cimi: $ init-checkconf ubuntu-system-settings-wizard.conf [15:36] mterry, but I cannot run others in anyway [15:36] Cimi: and $ initctl list | grep settings-wizard [15:36] Cimi, try rebooting? [15:36] xnox, maybe rebooting [15:36] Cimi: sudo -u phablet -i, should setup the right environment and join the existing upstart user session of the currently running phablet user. [15:36] (just because then the job will launch itself) [15:37] @pilot out === udevbot changed the topic of #ubuntu-devel to: Trusty Beta 1 released! | Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> saucy | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: [15:38] arges: so I have an idea for at least part of the problem, looking into ifupdown's code to confirm that one now. [15:38] arges: I suspect that ifup only writes ifstate in one shot at the end of the bring up which will then race with anything happening from upstart... [15:40] stgraber: this is update_state in main.c? [15:41] arges: yeah, though reading it now, it looks safe... [15:44] mterry, xnox thanks works, and sim detection too [15:47] mterry, seb128 simple one https://code.launchpad.net/~cimi/ubuntu-system-settings/wizard.sim-detection/+merge/211976 [15:50] Cimi, looks good, thanks [15:54] arges: so the reason why bond0 isn't in ifstate is because upstart fails to bring up bond0, I'm trying to figure out exactly why that is though [15:55] arges: oh, hold on, I think I know [15:55] stgraber: network-interface.conf or networking.conf? [15:55] stgraber: : ) ok [15:55] arges: yep, figured it out, your config has been wrong all along :) [15:56] arges: you can't have multiple default gateways [15:56] well, you can, but not with the same priority [15:56] Laney: Thanks! [15:56] dhcp gives you a default gateway, you also have one in bond0, so bond0 fails to come up because ifupdown can't set the gateway [15:57] however bond0 is also created at that point so the rest continues and blows up because bond0 was never initialized due to the failure [15:57] stgraber: so two things : 1) how come this works on reboot? 2) do you think ifupdown should show a better error message? [15:58] arges: it's a race. If for some reason bond0 comes up before eth0, then things appear to work because dhclient will just silently fail to set its gateway [15:59] arges: ifupdown actually did log an error, just not anywhere where we were looking (it was in /var/log/upstart/network-interface-bond0.log) [15:59] stgraber: well I just get things like 'Failed to bring up bond' [15:59] arges: to confirm, can you try adding "metric 10" to your bond0 on both test machines and then confirm everything works as expected? [16:00] arges: aren't you getting the netlink error for IP collisions? [16:00] RTNETLINK answers: File exists [16:00] stgraber: yes I get that error as well [16:00] ah [16:00] that's where ip addr sets that gateway and it fails [16:00]