/srv/irclogs.ubuntu.com/2015/10/14/#ubuntu-devel.txt

=== juliank0 is now known as juliank
pittiGOod morning04:17
roaksoaxpitti: howdy!04:22
roaksoaxpitti: quick question, any ideas? http://pastebin.ubuntu.com/12778124/04:22
roaksoaxpitti: running vivid's adt in trusty, against a vivid qemu image04:23
pittiroaksoax: if "runlevel" says "unknown" this means that the VM hasn't done early boot yet, presumably some service is failing?04:26
pittiroaksoax: you can run "--- qemu --show-boot ..." to watch the VM booting, perhaps you see an error there?04:26
roaksoaxpitti: systemd seems to bring everything up just fine04:27
roaksoaxpitti: the only thing:04:28
roaksoax[    1.037526] systemd[1]: Set hostname to <ubuntu>.04:28
roaksoax[    1.185590] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.04:28
pittithat should be fine04:30
pittiroaksoax: so that smells like a bug in autopkgtest then, apparently there's sometimes still stuff going on after login is ready04:31
roaksoaxpitti: right, so I'll try to create a new image and see what happens04:31
pittiroaksoax: if you boot the VM manually in QEMU, log in, and run "runlevel", what exit code and output do you get?04:31
pittiroaksoax: i. e. does it ever flip to exit 0/output "2", or stay in "unknown" forever?04:31
pittiroaksoax: i. e. does this just need to become a waiting loop, or is something genuinely broken there?04:32
pittiroaksoax: err sorry, should go to "5", but any number will do :)04:32
roaksoaxpitti: i'll give that a try04:32
roaksoaxpitti: created a new image, and now see this:05:06
roaksoax[FAILED] Failed to start Seed the pseudo random number generator on first boot.05:06
roaksoaxSee "systemctl status pollinate.service" for details.05:06
pittiroaksoax: ah, so I suppose "systemctl status" is "degraded", not "running"?05:06
pittiroaksoax: what does "runlevel" say then?05:06
roaksoaxsae:05:07
roaksoaxadt-virt-qemu: DBG: runlevel: exit 1, out "unknown05:07
roaksoax", err "None"05:07
roaksoaxhaven't run it manually yet05:07
roaksoaxpitti: weird, it works fine with wily with the same error05:10
dholbachgood morning06:24
clobranogood morning all06:44
pittisarnold: do you need any further security info in bug 1488341?07:52
ubottubug 1488341 in libmicrohttpd (Ubuntu) "MIR: libmicrohttpd" [Undecided,New] https://launchpad.net/bugs/148834107:52
=== davidcalle_ is now known as davidcalle
ginggsgood morning all08:52
ginggsdoko: i don't think that fpc 3.0.0 rc1 sitting in proposed is ready for production ( https://launchpad.net/ubuntu/+source/fpc ), is it possible to have it removed?08:54
=== tux_ is now known as soupnanodesukar
=== oSoMoN_ is now known as oSoMoN
=== mapreri_ is now known as mapreri
flexiondotorgI've just tried an upgrade from 15.04 to 15.10 which fails because Thunderbird in 15.04 is newer than the one on 15.10.09:55
ricotzchrisccoulson, ^10:09
* xnox got removed from all my channels, *sigh*10:19
=== marcusto_ is now known as marcustomlinson
seb128pitti, are ddebs still relying on the old importer script or did we got them in launchpad now? and if we got them in launchpad when did that landed? (doing a bunch of rebuilds for missing ddebs and I wonder if that's the still supposed ot be an issue)10:31
pittiseb128: we switched to Launchpad at the start of wily, so we don't need any rebuilds any more10:32
pittiseb128: if they are missing on ddebs, we can fish them out of LP10:32
seb128oh ok10:32
seb128are the retracers doing that10:32
pittiseb128: apport also falls back to direct LP download if it's not on ddebs.u.c. these days10:32
seb128I was looking at e.g https://errors.ubuntu.com/problem/11fc82b90619044eaa80c8acd806e58b47cace2110:32
seb128that started on september 2510:33
seb128and it seems to not find the ddebs on launchpad10:33
seb128those listed indeed miss amd64 ddebds on ddebs.u.c10:33
seb128e.g atk1.0 clutter-1.0 harfbuzz10:34
pittiseb128: right, apport's direct LP download fallback was added on Sep 30, i. e. after that10:36
seb128pitti, hum, ok, do you know if retracers can be nudged to fix those retraces?10:38
seb128or are the new tries going to success and be batched in a different bucket?10:38
pittiseb128: new tries ought to succeed now, yes; but I don't know for sure whether they'll become a new bucket10:39
seb128pitti, k, thanks10:39
pittiI thought once there was a known address signature already it won't actually retrace10:39
seb128k10:42
seb128pitti, do you know exactly when ddebs started being in launchpad/how to check if one is there?10:46
seb128like libsignon-glib was uploaded on 2015-05-13 unsure it needs a rebuild10:46
pittiseb128: you see it as normal build output in LP, e. g. https://launchpad.net/ubuntu/+source/atk1.0/2.16.0-2build1/+build/811585210:47
pittiseb128: and the previous atk was already built with ddebs too: https://launchpad.net/ubuntu/+source/atk1.0/2.16.0-2/+build/742809410:47
pittiseb128: not that it even matters for atk1.0 as that has a -dbg and thus the ddebs are empty10:47
seb128pitti, https://launchpadlibrarian.net/203832013/buildlog_ubuntu-vivid-amd64.libsignon-glib_1.12%2B15.04.20150420.1-0ubuntu1_BUILDING.txt.gz doesn't10:48
seb128so I guess that needs a rebuild?10:48
pittiseb128: start of May somewhere, I can't pinpoint it exactly (cjwatson might); but it's easy enough to check on a per-package basis10:49
pittiseb128: correct, 20 April was before enabling that10:49
pittihttps://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-006/+build/7343240 has no ddebs10:49
seb128pitti, danke10:52
cjwatsonseb128,pitti: Mysterious lack of logs of exactly when, but it was between 2015-04-30 and 2015-05-0510:56
cjwatson(With a brief period earlier when they were enabled but then backed out as we fixed a problem that arose)10:57
seb128cjwatson, pitti, k, I think that's enough information to see what needs a rebuild or not, thanks10:57
cjwatsonseb128: Right, not much was built in the ambiguous period since it was before wily opened.10:57
sil2100barry: hey! Once you're around, I would need sponsoring/review for LP: #1505632 and a sync for LP: #150600711:44
ubottuLaunchpad bug 1505632 in python-glance-store (Ubuntu) "FTBFS due to failing unit tests" [High,In progress] https://launchpad.net/bugs/150563211:44
ubottuLaunchpad bug 1506007 in python-linecache2 (Ubuntu) "Sync 1.0.0-2 from debian testing, fixes FTBFS due to unit tests failing to run" [Undecided,In progress] https://launchpad.net/bugs/150600711:44
sil2100barry: thanks! :)11:44
=== matsubara_ is now known as matsubara
dokodidrocks, LP: #1440549 your comment and the "solution" don't make sense.13:32
ubottuLaunchpad bug 1440549 in gconf (Ubuntu) "please convert python scripts to python3" [High,Fix released] https://launchpad.net/bugs/144054913:32
dokoif you want to use python3 use it.13:32
dobeydoko: hi. do you have any idea how to get gccgo-4.9 to be usable as /usr/bin/go on vivid? gccgo-5 isn't usable because it requires g++5, so all the binary compatibility issues make it untenable on vivid.13:34
=== _salem is now known as salem_
dokodobey, why? gccgo-5 doesn't depend on g++-513:36
dobeydoko: not directly, but it tries to execute it, which fails13:36
dokodobey, ahh, you mean when you have embedded c++ code?13:37
dobeyyes13:37
dokothat's somehing we probably can't fix. does the go driver allow to call another CXX?13:38
dobeyi have no idea.13:38
dobeydoko: btw, re: that python3 bug above, dh-python does rewrite shebangs, but only /usr/bin/python ones, not /usr/bin/env (because that'e executing env, not python), iirc13:40
barrysil2100: cool will look13:41
dokodobey, could you try setting CXX=g++-4.9 in the env?13:41
dobeydoko: seems to work, but now i get /usr/bin/ld.gold: error: cannot find -lstdc++13:43
seb128doko, what if you want to use "the default python version"?13:43
dokoseb128, we don't have a "default python version"13:43
seb128we should :-)13:44
dokowe're not ArchLinux ;p13:44
dobeyseb128: then you want to use python 2.x. it's what the PEP says, and what we do :)13:45
dokodobey, -L$(dirname $(g++-4.9 --print-file-name libstdc++.so))13:45
seb128then that "env python" and the depends on python are fine?13:45
dokowhat does the PEP have to do with removing python2 from the images?13:46
dobeyseb128: as long as gconf2 isn't part of the default install, i guess so. otherwise they conflict with the goal of removing python2 from the images13:46
dobeydoko: nothing with that, but the PEP has to do with /usr/bin/python vs /usr/bin/python313:46
dokoright13:47
didrocksdoko: so, we hardcode /usr/bin/python3?13:48
* didrocks backlogs13:48
dokodidrocks, this, or maybe use env python3 if you like13:48
dobeydidrocks: or /usr/bin/env python3 if you prefer13:48
dokoviolent agreement13:48
didrocksok, I thought that mutliple time, we required to use env instead of anything13:49
dobeyand change build-deps and any binary deps, to be python3 things13:49
didrocksdobey: if you looked at the package, that's already done for long13:49
didrocksso only changing to python3, will do in next upload13:49
dobeydidrocks: then the package is broken since the script runs against things the package doesn't depend on :)13:50
dobeybut yeah, just change the shebang then13:50
dobeydoko: so how do i get that -L passed to gccgo? setting LDFLAGS didn't seem to do it13:52
dokodobey, hmm, on second thought, just use $(g++-4.9 --print-file-name libstdc++.so), so that other files are taken from the default gcc lib dir13:52
dokono idea13:52
doko        cppflags = stringList(envList("CGO_CPPFLAGS", ""), p.CgoCPPFLAGS)13:53
doko        cflags = stringList(envList("CGO_CFLAGS", defaults), p.CgoCFLAGS)13:53
doko        cxxflags = stringList(envList("CGO_CXXFLAGS", defaults), p.CgoCXXFLAGS)13:53
doko        ldflags = stringList(envList("CGO_LDFLAGS", defaults), p.CgoLDFLAGS)13:53
doko 13:53
dokofrom go/cmd/go/build.go13:53
dobeygccgo-5: error: /usr/lib/gcc/x86_64-linux-gnu/4.9/libstdc++.so\: No such file or directory14:02
dobeyhrmm14:02
dobeywtf cmake/gccgo14:02
ogra_cyphermox, did you see bug 1446689 ?14:06
ubottubug 1446689 in network-manager (Ubuntu) "network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe" [Undecided,Confirmed] https://launchpad.net/bugs/144668914:06
dokodidrocks, dobey looks like you have to use dh_python3 --shebang=/usr/bin/python3 explicitly14:07
ogra_(and the corresponding ubuntu-devel-discuss thread)14:07
cyphermoxogra_: yes, I saw14:07
dokodobey, the extraneous : ?14:07
ogra_cyphermox, i wonder if we can do something about that ... seems rp-pppoe is in universe now for whatever reason14:08
dobeydoko: for some reason a "\" is being added to the filename soemwhere14:10
dobeybut afaict it's not cmake doing it, but gccgo14:10
cyphermoxogra_: we'll just have to promote it again, if it was ever in main14:10
ogra_yeah, well, if it was, that is most likely quite a while ago14:10
dokodobey, or -L$(dirname $(gcc-5 --print-file-name libgcc_s.so)) -L$(dirname $(g++-4.9 --print-file-name libstdc++.so))14:11
dobeyoh maybe it is cmake14:11
dobeyhmm14:11
cyphermoxogra_: ah, I think I see.14:12
dobeyno idea why that's happening though :(14:12
didrocksdoko: interesting, that's for the pointer! I'll bundle that in next upload14:13
ogra_cyphermox, oh ... the "--with-pppoe=/usr/sbin/pppd" sounds like an interesting workaround :)14:14
ogra_probably works without seeding rp-pppoe14:14
cyphermoxogra_: right, plus part of that code changed at some point14:17
ogra_ah14:17
ginggscyphermox, ogra_ : hi, i'm familiar with that bug14:19
cyphermoxhttp://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6fdfb03107138e96e641d12a7c4df5ecfacb540614:19
ogra_yeah, i see your comment :)14:19
rbasakhallyn: it looks like your netcf FTBFS fix in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795328 also came up on the rebuild test and affects 1:0.2.6-1 in Debian experimental which is synced to Wily. I can cherry-pick it but do you want to upload a fix to Debian experimental and sync that instead?14:21
ubottuDebian bug 795328 in src:netcf "netcf: FTBFS: error: 'IFF_UP' undeclared (first use in this function)" [Serious,Fixed]14:21
cyphermoxI'll cherry-pick the fix to wily and prepare a SRU for vivid.14:21
ogra_yay14:21
ogra_now that was quick ... :)14:21
cyphermox^^ commit is upstream already, it's just a matter of identifying which14:22
cyphermoxso once I looked at git and saw that the pppoe_binary bits weren't there, and we have them in what's currently in wily, then it's obvious there is some patch to apply14:23
cyphermoxor14:23
cyphermoxogra_: wanna do it?14:23
cyphermoxor morphis14:23
ogra_very busy this week ... sorry14:23
* ogra_ only saw the mail and wanted it handled if possible :) 14:24
cyphermoxdoes that affect you?14:24
cyphermoxginggs: me guesses you're directly affected by this, so you could test the SRU?14:24
ogra_nope, i dont use NM on my router14:24
ogra_(headles ufw/pppoe setup)14:25
bdmurraypitti: Where is your retracer code? https://bugs.launchpad.net/ubuntu/+bug/1320700/comments/2 That could use some improvement.14:25
ginggscyphermox: sure i can test an SRU14:25
ubottuError: malone bug 1320700 not found14:25
cyphermoxyeah14:25
ogra_malone !14:25
dobeydoko: i managed to get it a bit further along, but now it's weirdly complaining about use of undefined name in some of the go code14:25
ogra_now i feel old14:25
ogra_(remembering what malone is/was)14:25
bdmurrayogra_: I hate to tell you this but you are14:26
ogra_lol14:26
ogra_so true14:26
pittibdmurray: it's not in bzr, these are just some custom scripts that we run every now and then to clean up the unretraceableones14:26
bdmurraypitti: ah, okay14:26
dokodobey, paste?14:28
dobey../../service-ng/src/github.com/ziutek/glib/value.go:71:3: error: reference to undefined name ‘_Cfunc_g_value_set_double’14:29
dobeylot sof stuff like that14:29
dobeyi wonder if we can get golang 1.5 backported to the vivid phone overlay PPA instead of trying to make gccgo work14:38
=== Guest77290 is now known as balloons
dokodobey, wasn't the server team already doing that?14:41
jrwrendobey: copy it from ppa:~ubuntu-lxc/lxd-stable ?14:42
dobeydoko: why would the server team care about go on the phone?14:42
jrwrenhow is go on the phone different from an armhf build of go?14:42
dobeyor they are backporting as an sru for vivid?14:42
thebwtHowdy folks, is there a document out there that details packaging destination directory best practices?  like when to use /sbin vs /usr/sbin ?14:43
dokowelcome to the wonderful world of inter team communication14:43
thebwt(asked in the packaging, but it's been a ghost town for the last week)14:43
dobeyjrwren: well, armhf isn't the problem. it's arm64 and ppc14:43
chilukinfinity, arges, do either of you have a chance to review the debdiff for https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1432871 with me?14:44
ubottuLaunchpad bug 1432871 in coreutils (Ubuntu Wily) "`df` shows bind mounts instead of real mounts." [Low,In progress]14:44
jrwrendobey: for phone? oh right, arm6414:44
dokodobey, but maybe mwhudson knows about the cfunc stuff ...14:44
jrwrendobey: there is a go with builds for all those platforms in that ppa14:44
argeschiluk: i can take a look14:44
dobeyjrwren: well, for phone there is an overlay PPA and QA requirements and such, so for me to use new go on vivid, we need to get new go approved to go in that PPA14:44
argeschiluk: oh i remember this one : )14:45
jrwrendobey: ah, sorry. I see what you mean.14:45
chilukarges it's a fairly large change... but debdiff is a collection of clean-ish cherry-picks from upstream.14:45
argesyea this will require more coffee14:45
chiluklol..14:45
chilukI think I did a good job documenting what I did in the case, and in the patch.14:46
sil2100doko, slangasek: hey! So, regarding the mir build-failure from bug LP: #1506045 - could anyone of you guys copy-package the mir version I mentioned there from the overlay PPA to the archive? It has the fix for the build failure14:50
ubottuLaunchpad bug 1506045 in mir (Ubuntu) "FTBFS on amd64, armhf and i386 due to missing headers" [Undecided,In progress] https://launchpad.net/bugs/150604514:50
Laneysil2100: seb128 has been pinging the team about it14:51
Laneymaybe find out what they said first14:51
seb128I asked them yesterday14:51
seb128they said they needed QA verification first14:51
seb128kgunn said they would copy over once it's done14:52
seb1280.1714:52
kgunnseb128: yep, it just now got QA approval14:52
kgunnso needs to at least migrate to overlay first14:52
seb128great14:52
sil2100QA verification?14:52
seb128it's a dual landing14:52
seb128you know QA team, touch, phone etc14:53
sil2100But it's landed already14:53
seb1280.17?14:53
sil2100No, 0.16.1+15.10.20150930.114:53
seb128they want to land 0.1714:53
sil2100This is enough to get wily mir building14:53
seb128right14:53
seb128but 0.17 is ready and has more fixes14:53
seb128they wanted to land that directly14:53
sil2100Ok, well, I just want to resolve the build failure before the release14:54
sil2100Anyway, as long as 0.17 builds on wily as well then sure ;)14:54
seb128right and it's being handled14:54
seb128don't worry about it14:54
Saviqbbl15:16
ginggscyphermox: shouldn't you remove '--with-pppoe=/usr/sbin/pppoe' from debian/rules as well?15:21
cyphermoxginggs: yes, you're right, it will need to be changed to /usr/sbin/pppd or the right path for pppd15:22
ginggscyphermox: no i think it should just go15:22
cyphermoxoh, you're right15:25
ginggsdoko: it would be great if those FTBFS pages (e.g. http://qa.ubuntuwire.com/ftbfs/ ) had an editable comment field like the merge-o-matic pages (e.g. https://merges.ubuntu.com/universe.html )15:30
dokowgrant, ^^^15:43
dokoginggs, yeah, but there is not much space on these lines15:43
dokomvo, just updated https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/82325415:47
ubottuLaunchpad bug 823254 in software-center (Ubuntu) "Port to python3" [Medium,Confirmed]15:47
dokowhat is this issue about gmenu?15:47
mvodoko: I don't know about a gmenu issue sorry15:58
dokomvo, well, you wrote about it in the past?15:58
mvodoko: aha, this can be removed, current trunk is using gobject-introspection already for gmenu16:00
mvodoko: and python3-dbus exists also, let me update the bug16:01
dokomvo, ta16:02
mvoyw16:02
mterry@pilot in16:20
=== udevbot_ changed the topic of #ubuntu-devel to: Archive: feature freeze, user interface freeze, final beta freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-vivid | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: mterry
seb128happyaron, cking, do you have a ffe for zfs-linux? https://wiki.ubuntu.com/FeatureFreeze states that's needed for new packages (and those should stop after beta freeze)16:32
ckingseb128, https://bugs.launchpad.net/zfs/+bug/150571616:32
ubottuLaunchpad bug 1505716 in Ubuntu " [FFE]: dkms: add ZFS support in universe" [Undecided,New]16:32
seb128thanks16:32
=== Saviq_ is now known as Saviq
=== Logan_ is now known as Logan
seb128cking, happyaron, sorry but the zfs news review is not going to be for today from me, we have team dinner tonight and I need to go17:02
seb128maybe somebody in the U.S tz can pick that up17:02
seb128otherwise I'm going to try to have a look tomorrow if things are not too crazy at the sprint17:02
ckingseb128, tomorrow is fine, thanks17:03
seb128yw!17:03
=== ming is now known as Guest10359
mterrychiluk, I'm looking at bug 143287117:10
ubottubug 1432871 in coreutils (Ubuntu Wily) "`df` shows bind mounts instead of real mounts." [Low,In progress] https://launchpad.net/bugs/143287117:10
mterrychiluk, and I see you also patched gnulib17:10
mterrychiluk, but don't have a wily patch for it?17:10
chilukmterry are you looking for https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1432871/comments/917:12
ubottuLaunchpad bug 1432871 in coreutils (Ubuntu Wily) "`df` shows bind mounts instead of real mounts." [Low,In progress]17:12
chilukor has the wily version changed in the last few weeks.17:13
mterrychiluk, that's a patch for the coreutils package17:13
mterrychiluk, does the gnulib package not also need a patch?  You link to upstream gnulib changes17:13
chilukmterry I guess you are correct..17:13
chilukthe weird thing is that we package coreutils with a gnulib already sitting in lib17:14
mterrychiluk, are they separate changes?  It looks like you mention coreutils needing support in gnulib?17:14
chilukunless I'm missing something.17:14
chilukI didn't notice that we had a separate gnulib package..17:14
chilukI'll work on a debdiff for gnulib this afternoon.17:15
* mterry looks at code...17:15
mterrychiluk, I see what you mean.  It does seem to include its own copy of the code17:16
chilukit's definitely not dynamically linked to gnulib sources.. it's really a very odd project like that.17:17
chilukmterry I think you are right though, if we are going to fix coreutils we should probably have the requisite changes in gnulib as well.17:18
mterrychiluk, I think maybe it's OK to ignore gnulib for now...17:18
mterrychiluk, it doesn't seem as important -- we can wait for upstream there17:18
chilukalrighty..17:18
chilukmterry if you want to do the initial upload I'll get arges to do the SRU when I meet up with him this afternoon.17:19
mterrychiluk, uploaded (with a bugfix merge from Debian included too)17:20
chilukawesome thank you mterry17:20
mterrychiluk, thanks for the fix!  :)17:20
chilukyeah.. it was a royal pita.17:20
mterrychiluk, whoops.  I was careless.  I uploaded the coreutils change, but it is ftbfs18:18
mterrychiluk, have you tested it on wily?18:18
mterrychiluk, specifically, the tests/misc/chroot-fail.sh dies on everything from chroot / sh... down18:42
chilukmterry, yeah this is weird.. I know I built it last week....18:42
chilukmterry give me a sec.. I'll get it squared away.18:42
chilukyeah the .m4 changes shouldn't have been in there.18:44
chilukthe patches that got included add them, then remove them.18:44
chilukthat's where it's failing.18:44
chilukmterry I think I may have just uploaded the wrong debdiff.. this bug has been going on for so long.18:45
mterryhah18:45
chilukmterry, no that's the correct patch... I even have the debs that I built with it.18:51
chilukmterry I'm attempting another sbuild now.. mterry .. I know I had issues getting coreutils to build using pbuilder ... are you using pbuilder by chance?18:51
mterrychiluk, I am, but I saw the same error that the buildd did when using it (and an extra error when building locally, but I didn't worry about that one)18:52
mterrychiluk, I've combined your patch with another change from Debian when uploading... maybe that is screwing something up?18:55
mterrychiluk, it was a chroot related change in debian...18:56
mterrychiluk, but Debian's package builds fine for me18:56
argeschiluk: https://launchpad.net/ubuntu/+source/coreutils/8.23-4ubuntu1/+build/812976318:56
chilukmterry .. it's ok .. I'll take a closer look at it.18:56
chilukmterry looks like a test failure..18:57
mterrychiluk, yup18:57
chilukmterry FAIL: tests/misc/chroot-fail .... my changes should be touching that.18:58
=== DrKranz is now known as DktrKranz
chilukmterry PASS: tests/misc/chroot-fail.sh  ... builds fine with just my patch.19:02
chilukI'll grab the sources and see what's going on.19:02
mterrychiluk, sorry  :(  I didn't consider Debian's patch blowing yours up19:02
chilukmterry ... I'll help figure this out.. perhaps we should push my patch back into debian..19:03
chilukI think It's mostly ready for submittal there, but they don't have a related bug open yet.19:04
NoskcajWould someone  be able to sponsor a merge of redshift for me? it's currently non-funtional in wily, and it would be great to fix it19:04
mterryNoskcaj, got a bug number?19:06
argeschiluk: http://launchpadlibrarian.net/221228821/coreutils_8.23-4ubuntu1.dsc19:06
Noskcajbug 148515319:06
ubottubug 1485153 in redshift (Ubuntu) "Unable to connect to GeoClue" [High,Triaged] https://launchpad.net/bugs/148515319:06
Noskcajprobably a few dupes too. I'm just merging it now, i've been away for a few months19:07
mterry:)19:07
arges@pilot in19:20
=== udevbot_ changed the topic of #ubuntu-devel to: Archive: feature freeze, user interface freeze, final beta freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-vivid | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: arges, mterry
argesmterry: oh its your patch pilot day too : )19:20
mterryarges, :)19:20
mterryarges, I'm currently working on "baloo_file_extractor crashed with SIGSEGV in memcpy"19:21
Noskcajhttps://code.launchpad.net/~noskcaj/ubuntu/wily/redshift/merge2/+merge/27444819:21
mterryJust to avoid overlap19:21
mterryarges, and Noskcaj's merge ^19:21
argesmterry: ok19:21
chilukmterry so I just removed my patch from your upload of coreutils, and chroot-fail.sh still fails.... so it's like the debian patchset that's breaking somethin.19:22
mterrychiluk, huh... I had tried that...19:22
* chiluk is happy it wasn't his fault for once...19:22
mterrychiluk, will try again to confirm19:22
chilukI just commented my patch out of 00list.. with a #... not sure if that would do it..19:23
mterrychiluk, I think so?  As long as it was not applied at the time19:23
mterryI don't believe your patch was anything but a debian/patches patch19:23
* arges looks at 131488719:26
chilukmterry that is correct...19:27
mterrychiluk, ah.. I know why my test of debian's change worked.  They don't run tests, but the fact that we do wasn't clear from our changelog delta.  OK.  I'll patch out the test due to it being Debian19:33
chilukmterry it looks like you removed -33_chroot_always  .. that's probably the source of the build failure.19:34
chilukmterry give me one sec to check.19:34
mterrychiluk, no?  That was added by Debian19:36
chilukyeah but they aren't running tests.19:37
chilukjust give me a sec to understand what's going on and what's being tested here.19:37
mterrychiluk, right.  But I'm saying I didn't remove 33_chroot_always, I added it.  I think the fix is just patching out the tests in chroot-fail.sh that assume Debian didn't patch out the "chroot /" optimization19:38
chilukyeah I think you may be correct.19:39
mterrychiluk, alright will go ahead with that then19:41
chilukmterry  the 33_chroot patch is definitely the source of the test failure.19:51
mterrychiluk, cool.  I'm testing a build of coreutils with the tests patched out.  I presume it will work and I'll upload19:51
mterrychiluk, sorry to alarm ya19:51
chilukmterry are you patching out all the tests or just the chroot-fail test?19:52
mterrychiluk, just the chroot-fail ones that actually fail19:53
chilukmterry ... no worries... just support me when I submit for core dev eventually..19:53
mterrychiluk, hah, the standard fee for that is measured in beers  :)19:53
chilukmterry... I'm not above bribery ...19:56
tyhickspitti: hello - is the libmicrohttpd MIR something that can happen towards the start of the 16.04 devel cycle or do you need it in main for 15.10?20:08
arges@pilot out20:18
=== udevbot_ changed the topic of #ubuntu-devel to: Archive: feature freeze, user interface freeze, final beta freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-vivid | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: mterry
chilukmterry are you going to be doing a copy of the wily sources to vivid as well?20:19
mterrychiluk, wasn't planning to20:20
mterrychiluk, didn't want to include the Debian stuff there20:20
chilukmterry they were at the same version.20:20
chilukmterry can I get up to upload my patch for vivid as well then?20:20
chilukI kind of want it to bake a bit in vivid/wily before proceeding with trusty20:21
mterrychiluk, I can upload for vivid too sure20:21
chilukthanks.20:21
mterrychiluk, that was my thinking for letting it bake in wily.  But sure on vivid20:21
chilukoh ok.20:21
chilukwe can wait a few weeks then with wily.20:21
mterrychiluk, no I'm fine.  it's just vivid  :)20:25
chilukyeah ... it should be safe... I just figured we'd get more thorough testing there.20:25
mterrychiluk, but first let it land in wily20:26
chilukyeah.20:26
mterrystill hasn't20:26
dokoslangasek, I think you are wrong writing "will cause the behavior of programs to be inconsistent"20:32
mterry@pilot out20:44
=== udevbot_ changed the topic of #ubuntu-devel to: Archive: feature freeze, user interface freeze, final beta freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-vivid | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
mwhudsondobey: are you still here?21:15
dobeyhi21:16
pittityhicks: libmicrohttpd can certainly wait for 16.04; we are deep in FF anyway, I just stumbled across it today and wondered if it was blocked on information or just manpower21:17
tyhickspitti: that's great to hear!21:18
dobeymwhudson: i think the best solution is to just try and get golang 1.5 into our phone overlay ppa at this point, to solve the issues we're hitting21:19
tyhickspitti: it is a man power issue - we had several high priority MIRs that trumped many others this cycle21:19
mwhudsondobey: ah ok21:19
pittityhicks: that's ok, thanks21:19
mwhudsondobey: let me know if you want me to try to figure out what's going on, but if it's 1.4 or earlier i might not be much help21:20
dobeymwhudson: yeah, the problem is vivid has 1.3, and on arm64 and powerpc doesn't use golang-go, but rather uses gccgo, and that isn't working with cgo very nicely21:22
mwhudsondobey: aah21:22
mwhudsonyeah sounds plausible21:23
mwhudsonfwiw, golang-go on ppc64el is still pretty bad at cgo21:23
dobeyi'm more worried about arm64 than ppc really at this point21:24
dobeyaren't many ppc phones on the market :)21:24
sergio-br2hi21:28
sergio-br2just a quick question: ubuntu packages are synced from sid or testing?21:28
pittisergio-br2: the autosync is from sid usually, but we don't run it right now; manual syncs can happen from anywhere21:30
sergio-br2even universe packages are from sid?21:31
sergio-br2and main21:31
pittiyes21:31
pittiwe have our own britney instance to keep out the brokenness21:32
sergio-br2ok, found something http://askubuntu.com/questions/104287/how-is-ubuntu-more-updated-than-debian21:32
sergio-br2so the LTS packages comes from testing21:32
cjwatsonnot any more21:32
cjwatsonthat was true at one point but it proved to be more trouble than it was worth, especially once we introduced our own equivalent of testing migration21:32
cjwatsonnote the date on that answer21:33
sergio-br2february 201521:33
cjwatsonno21:33
sergio-br2nope, it's 2012 right?21:33
cjwatsonit's a silly American date21:33
cjwatson2012-02-15 in sensible formatting21:33
sergio-br2so 14.04 came from sid more or less?21:34
cjwatsonsergio-br2: yes21:36
cjwatsonsergio-br2: 12.04 was testing if I'm remembering/reading the history correctly21:38
sergio-br2it explain lot's of stuff21:38
cjwatsonauto-syncing from testing meant that it took longer for regressions to get fixed due to the standard migration delay in Debian, and we ended up frequently spending time chasing down regressions that turned out to be already fixed in unstable21:40
cjwatson(and obviously it had some benefits, but our own testing migration provided the bulk of the same benefits)21:41
=== salem_ is now known as _salem
sergio-br2thanks for the explanation21:51
=== alai` is now known as alai
sergio-br2another question: why the kernel number is not bumped to 4.2.0 --> 4.2.1 --> 4.2.2 and so ?22:56

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