=== jono is now known as Guest11562
=== sunweave1 is now known as sunweaver
=== jono is now known as Guest60019
ePierreHi everyone!10:43
ePierreI'm working in the Checkbox team <https://launchpad.net/checkbox-project> and we just raised two issues to get packages removed from Xenial repositories: pad.lv/1512641 and pad.lv/1512642 ; please let me know if there are anything else I need to do or provide for this to happen. Thanks!10:45
Mirvhas anyone running 14.04 LTS been able to workaround bug #1497420 to attach to xenial lxc?10:52
ubottubug 1497420 in lxc (Ubuntu) "systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach" [High,Triaged] https://launchpad.net/bugs/149742010:52
mardyseb128: hi! Did you have time to look at https://requests.ci-train.ubuntu.com/#/ticket/446 ?11:01
Laneyutlemming / Odd_Bloke / smoser: know when we'll get the first cloud images?11:49
* Laney is trying to use adt-buildvm-ubuntu-cloud :)11:50
Odd_BlokeLaney: We're doing a major rework of how we build images for xenial, so dailies on cloud-images.ubuntu.com aren't imminent.11:52
Odd_BlokeLaney: I did point pitti at some sample images for him to test out, but I don't know that he's managed to get to them yet (I believe he's sprinting this week).11:53
=== _salem is now known as salem_
LaneyOdd_Bloke: OK, thanks, I'll check if a-b-u-c can use those somehow12:00
=== dpm__ is now known as dpm
pittiOdd_Bloke: oh, you did? sorry, missed them12:14
pittiOdd_Bloke: ETA 4 hours, go hotel network :)12:22
mgedminhuh, collectd in debian testing is 5.5.0; collectd in xenial is still 5.4.112:24
mgedminah, judging from the .ubuntu1 version it needs a merge12:31
seb128mardy, sorry for the delay, published now12:31
mardyseb128: nw, thanks a lot! :-)12:32
mardyseb128: ah looks like it failed12:33
mardyseb128: packages changed in the archive, let me sync them...12:34
seb128mardy, if they are no change upload we can override12:34
seb128but please check if there is content to include12:34
mardyseb128: ok, I'll let you know in a minute12:35
=== Zic is now known as Guest20486
* mgedmin finds and reads https://merges.ubuntu.com/c/collectd/REPORT12:37
mardyseb128: yes, all three are "no change rebuild"12:37
seb128mardy, ok, published again with override which worked12:40
Odd_Blokepitti: :)12:44
mardyseb128: thanks!12:47
seb128mardy, yw!12:48
=== Guest20486 is now known as Zic
=== hikiko is now known as hikiko|ln
=== lool- is now known as lool
=== rickspencer3_ is now known as rickspencer3
=== zul_ is now known as zul
rbasakpitti: taking the nis merge to work on with cpaezler. I trust that's OK.14:18
pittirbasak: please14:18
pittirbasak: no, thanks to you :)14:19
=== hikiko|ln is now known as hikiko
=== mwenning is now known as mwenning-wfh
pittiOdd_Bloke: http://people.canonical.com/~dwatkins/20151028/ amd image is working fine here! I tested it with local qemu, not with an actual cloud, but I guess you already did that14:33
seb128what's the way to let britney to let a package through if it reduced the list of archs it's building a binary on? deleting the binary for those archs in the release pocket?14:41
cjwatsonseb128: that14:46
cjwatsonthough obviously check reverse-dependencies first14:46
seb128right, I just did14:46
seb128it's for xserver-xorg-video-vmware14:47
seb128(I hope I didn't overlook thing)14:47
seb128cjwatson, thanks14:47
mardy_seb128: the message about the packages being "in the proposed pocket", does it mean that it's all right, or is it an error? https://requests.ci-train.ubuntu.com/#/ticket/44615:03
seb128mardy_, it's normal, things go through proposed and migrate when/if they are ok (tests passing, not creating un-installability issue, etc)15:04
mardy_seb128: ok, thanks15:05
seb128mardy_, see https://wiki.ubuntu.com/ProposedMigration if you are interested by the detailzs15:05
ogra_cjwatson, infinity, does either of you know how live-build enforces immediate execution of triggers ? (i have a problem installing the raspi2 kernel package during a livefs build, afaik it is 100% based on the -generic package so it should work, yet it defers the update-initramfs trigger, so the postinst fails) https://launchpadlibrarian.net/224109673/buildlog_ubuntu_xenial_armhf_ubuntu-core-system-image_BUILDING.txt.gz15:12
ogra_the apt.conf manpage only seems to have options to suppress trigger execution15:13
TJ-ogra_: I may be mis-remembering but from a looong way back I seem to recall seeing/using OrderList::Score::Immediate15:18
ogra_TJ-, hmm, i'll try15:18
cjwatsonogra_: as far as I know, it doesn't15:23
ogra_weird, so that would be a packaging bug in the raspi2 package ?15:24
cjwatsonthat would be my first guess15:24
ogra_hmm and the kernel team is traveling :(15:24
cjwatsondeferring triggers isn't really a thing15:24
ogra_enforcing :)15:24
cjwatsonI mean, enforcing immediate execution of triggers isn't really a thing15:24
cjwatsonOrderList::Score::Immediate is a bit different really15:25
ogra_yeah, thats how i read the manpage15:25
Laneydoko: Do you have an idea on how we can get past https://sourceware.org/bugzilla/show_bug.cgi?id=19188 ?15:31
ubottusourceware.org bug 19188 in ld "[2.26 Regression] binutils assertion fail ../../bfd/elfnn-aarch64.c:4631" [Normal,Assigned]15:31
Laneyit's breaking webkit2gtk/arm64 which is going to be the last thing holding up a big-ish migration soon15:32
seb128gdb doesn't work on xenial for me :-/15:43
seb128(gdb) bt15:43
seb128Python Exception <class 'SystemError'> <built-in function isinstance> returned a result with an error set:15:43
seb128those python errors is everything it returns15:44
sarnoldseb128: maybe disable autoloading python? https://sourceware.org/gdb/onlinedocs/gdb/Python-Auto_002dloading.html#Python-Auto_002dloading15:45
seb128sarnold, thanks15:45
seb128Laney, you could have updated python-pgmagick to 0.5.12 that patch is basically all there is in the new version ;-) (I pinged slangasek about that yesterday)15:45
seb128sarnold, that works ;-)15:46
sarnoldyay :)15:46
* Laney shrugs15:46
Laneywhy didn't you upload it?15:47
seb128Laney, because slangasek said it was on his list15:47
Laneydidn't see a bug15:47
seb128he was the one who uploaded the version that failed to build15:47
seb128yeah, I should probably have opened one15:47
seb128sorry about that :-)15:47
seb128I though he would handle it yesterday15:47
dokoLaney, sorry, not yet. gold fails too. for unity it only showed up build the test cases, so I proposed to disable these.15:47
dokoLaney, this is https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/151154215:47
ubottuLaunchpad bug 1511542 in unity (Ubuntu) " [2.26 Regression] binutils assertion fail ../../bfd/elfnn-aarch64.c:4631" [High,In progress]15:47
seb128doko, hey, gdb giving the python errors I just copied, is that known? what component should that be reported against?15:48
Laneydoko: :(15:50
dokoseb128, do you have a test case, or is this just loading the pretty printer?15:53
seb128doko, I just do "gdb something" and "run" and ctrl-C and bt15:53
seb128or attach to an existing process15:53
stgrabercyphermox: hey, who's in charge of network-manager these days? we've got a very serious regression affecting wily and xenial15:53
=== mitya57_ is now known as mitya57
stgraberslangasek, cyphermox: bug 151274916:00
ubottubug 1512749 in network-manager (Ubuntu Xenial) "lxcbr0 dissappears on Ubuntu 15.10" [Critical,Triaged] https://launchpad.net/bugs/151274916:00
barryLaney: matplotlib 1.5.0~rc2-1ubuntu3 \o/16:06
barryLaney: i was just about to start looking at that one :)16:06
Laneybarry: hehe16:07
Laneyyou should make more things depend on glib16:07
Laneythen you get people like me to care :P16:07
barryLaney: :)16:08
barryLaney: now i know how to trick you into fixing all the bugs16:08
sil2100slangasek, doko, cyphermox, any-other-core-dev: could you release https://bugs.launchpad.net/ubuntu/+source/ledit/+bug/1512776 for me? Thanks!16:18
ubottuLaunchpad bug 1512776 in ledit (Ubuntu) "Release no-change rebuild for ocaml transition" [Undecided,In progress]16:18
yofelpitti: fixes for some of the kubuntu autopackagetest failures uploaded, sorry that it took a while (some still need to be uploaded once I fixed our packageset..). Is there some way to list all kubuntu packages with test failures?16:19
pittiyofel: I think the easiest thing to start from is http://autopkgtest.ubuntu.com/data/status/xenial/amd64/packages.json16:20
yofelah nice, that works16:21
pittiyofel: probably easiest with three lines of python -- iterate over status "fail" and "kde" in package, or so?16:21
pittiI'm fairly sure one can do it with json_pp, but I never learned the magic of this; Laney knows this16:22
yofelif the naming would be that easy I wouldn't have trouble :P16:23
yofelbut we have lists of all our maintained sources, so filtering that won't be hard16:23
Laneypitti: yofel: The tool that I used was called 'jq'16:24
pittiah, or that16:25
yofelthanks, I'll look at that16:25
pittinot knowing that i'd just do something like "for p in json.load(f.read()): if p['package'] ...16:25
cyphermoxsil2100: looking16:32
cyphermoxsil2100: done.16:38
bdmurraytumbleweed: did you say you had updated distro-info-data?16:39
sil2100cyphermox: thanks!16:41
sil2100doko: https://bugs.launchpad.net/ubuntu/+source/unity-api/+bug/1512784 - MIR request pretty please16:42
ubottuLaunchpad bug 1512784 in unity-api (Ubuntu) "[MIR] unity-api" [Undecided,New]16:42
* ogra_ wonders whats up with the arm builders ... 16:45
cjwatsonogra_: ?16:51
ogra_cjwatson, well, they seem busy https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/xenial/ubuntu-core-system-image/ (i had them starting immediately all day during test builds)16:52
cjwatsonogra_: they have about a ten-minute queue at the moment due mostly to a batch of KDE uploads, but nothing serious16:53
cjwatsonogra_: see https://launchpad.net/builders/16:53
ogra_ah, k16:53
ogra_well, i'll wait16:53
cjwatsonarm64 will take longer, but that's normal16:53
cjwatsonI think the 28 minutes on your page is a misestimate16:53
ogra_yeah, for test builds i dont care for arm64 ... i should have excluded it from ARCHES=16:53
=== hikiko-lpt is now known as hikiko
bdmurraytumbleweed: I ask as I don't seem them in the unapproved SRU queues17:05
stgrabercyphermox: did you see my question above?17:08
cyphermoxI had not17:08
cyphermoxso, the short answer is "nobody really".17:08
cyphermoxNM shouldn't touch the interfaces it doesn't manage, especially not bridges, at all, so something clearly got broken17:09
stgraberI just uploaded a very very ugly workaround to xenial now, if that does the trick, we'll have to SRU this very quickly to wily too until NM gets fixed17:09
cyphermoxwhich package?17:09
stgrabercyphermox: http://paste.ubuntu.com/13092923/17:10
cyphermoxoh yuck17:10
stgraberas I said, very very ugly workaround, does the trick though17:11
stgraberthe alternative was a "sleep 5" but well, that'd just be racy :)17:11
cyphermoxso, I think we're running into more of the veth vs. straight ethernet device issue17:12
stgraberand nmcli doesn't seem to have a "wait until we reach some kind of final state"17:12
stgrabercyphermox: nah, it's a bridge here and NM does try to do stuff with the bridge backend code17:12
stgrabercyphermox: run: ip link add dev test type bridge && ip link set dev test up && ip addr add dev test && sleep 2 && ifconfig test && ip link delete test17:13
stgrabercyphermox: you'll get an interface without an IP17:13
stgraberNov  3 12:13:17 castiana NetworkManager[21958]: <info>  (test): new Bridge device (carrier: OFF, driver: 'bridge', ifindex: 94)17:14
stgraberso NM does detect it as a bridge and then still does stuff to it...17:14
stgraberit doesn't seem to start DHCP on it though, but it still does flush any pre-existing config from it17:14
seb128cyphermox, you are not maintainin n-m anymore? do you still plan to do the point release updates?17:15
cyphermoxI do what I can given available time; but these days there's a lot of things going in front of NM in the todo queue.17:16
seb128k, just wondering if we should do updates like we handle GNOME ones17:18
=== Ursinha is now known as Ursinha-afk
bdmurraytumbleweed: Ah, I see its in -proposed for everything except wily.17:40
Laneypresumably because we have it in there as Xenial X, so might as well wait for the real release date before SRUing again17:41
bdmurrayLaney: got it thanks17:42
cyphermoxseb128: by all means, feel free to do the updates for NM, but some may be quite involved :/17:53
seb128cyphermox, right...17:54
mterrypitti, hi!  I'm looking at the strip-nondeterminism MIR.  Looks fine, but I had a question about if enabling this means we'll fail a build if the tool has a problem or if it continues the build in that case (there are several bugs in Debian about strip-nondeterminism having problems on weird files)18:07
pittimterry: haven't checked for sure, but I'd expect it to FTBFS if dh_strip_nondeterminism fails18:09
pittimterry: but Debian has run it in production for some time, so I figure the worst bugs have been shaken out already18:10
pittimterry: and as I said on the bug, if this causes extra FTBFS the foundations team will certainly deal with this18:10
pitti(in the worst case by disabling it for that package or in general)18:10
mterrypitti, OK.  Well that's a decision for integration into debhelper anyway.  Not a reason to block the MIR.  This package itself is maintainable18:10
mterrypitti, cool, thanks!18:10
pittimterry: right; once approved, I'll revert the delta of dropping the dep from debhelper18:11
tumbleweedbdmurray: oh, yes, I forgot to verify them18:16
mterrybdmurray, the foundations team is looking after strip-nondeterminism in main, FYI18:17
bdmurraytumbleweed: I've verified Trusty and Vivid.18:18
tumbleweedbdmurray: thanks18:20
cyphermoxstgraber: what about this? http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=e29ab54335c6a5ef1ce6bac525f1f18a8e81b96e18:32
stgrabercyphermox: the reproducer in that commit is identical to what we're doing, so that's probably right18:37
mterrybdmurray, and unity-api is being looked after by unity-ui-team in main, FYI!19:04
=== _salem is now known as salem_
decciI am trying to build .DEB package19:35
decciI ran dh_make -f ../.tar.gz , then  debian/rules clean, build and binary. It went good and built .DEB package19:36
decciNow when I again re-run the debian/rules binary it threw error override_dh_auto_install19:38
decciError code 219:38
decciAny idea how to  fix this19:38
ricotzdecci, you should use "debuild" or "dpkg-buildpackage" to build a source package19:38
decciricotz: Do you mean use it instead of debian/rules build19:39
mterryjdstrand, and alabaster in main is also looked after by foundations team, fyi!19:40
decciricotz: So whats the correct way of building .DEB19:40
* mterry is clearing out MIRs :)19:40
decciricotz: All I follow: 1. dh_make 2. debian/rule clean 3. debian/rules build 4. debian/rules binary19:41
decciricotz: Where do I need to run debuild?19:41
decciricotz: I mean after which step19:41
ricotzdecci, you downloaded a source package, e.g. having a *.dsc file lying around?19:42
ricotzdo "dpkg-source -x *.dsc", go into the src folder and run "dpkg-buildpackage" or "debuild"19:42
decciricotz: I have source code, when I run dh_make it creates debian folder where rules, preinst and postinst gets created and .dsc gets created at ../19:43
ricotzso you want to create a debian package from some tarball without any existing packaging information?19:44
decciricotz: This is a source code internal to company..pre-compiled and linked already19:44
decciricotz: All I am trying to do is build it to .deb19:45
decciricotz: yes19:45
ricotzdecci, you might want to use "checkinstall" then19:45
decciricotz: checkinstall doesnt handle rules, preinst and postinst19:46
decciricotz: I dont see any option for rules specification19:46
ricotzyou don't have any packaging information in the first place19:46
decciricotz: I have rules, postinst and preinst, control files in place19:47
ricotzso simply use the tarball and build it and checkinstall creates a deb19:47
ricotzok, because you ran dh_make19:47
decciricotz: All I want to build .DEB package using these rules, preinst and postint19:47
ricotzthen debuild from within the root srcdir should work19:48
decciricotz: dh_make gives me debian folder with rules, post and preinst file created to add the rules19:48
ricotzsearch for debian packaging details to make further adjustments if needed19:48
decciricotz: I can try debuild , so do I need to run under my source19:49
decciricotz: which has Makefile, configure.ac19:49
decciricotz: CMakeCache.txt19:49
decciricotz: What could be reason of override_dh_auto_install Error: code 219:50
ricotzdebuild looks for the debian folder and its content19:51
ricotzsound like an error in your changes to rules19:51
ricotzbetter paste a more detailed error output (via pastebin), so someone can look at it19:52
ricotzI need to go19:53
decciricotz: dpkg-source: error: unwanted binary file: debian/CMakeFiles19:53
decciricotz: dpkg-source: error: detected 4 unwanted binary files (add them in debian/source/include-binaries to allow their inclusion).19:54
mterrybdmurray, and foundations for python-hypothesis too!19:54
bdmurraymterry: got it, thanks19:56
deccidpkg-buildpackage: error: dpkg-source -b dcde_source gave error exit status 2919:56
mterrybdmurray, (is this the easiest way to update the list? -- I'm fine with it, just curious if these pings get annoying)19:57
bdmurraymterry: the list of teams I'm already aware of can be found here - http://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/view/head:/package-subscribers#L10720:00
bdmurraymterry: If the team isn't in that list then being notified would be useful20:01
mterrybdmurray, ahh...  so if a team subscribes to a bug, you assume they are looking after it as long as they are in this list.  It's not a granular team->package thing20:01
bdmurraymterry: right, we look at the packages to which those teams are subscribed20:02
mterrybdmurray, cool OK, then I can drop a lot of pings  :)20:03
bdmurraymterry: indeed!20:03
cyphermoxstgraber: looks like it's good; I'll upload to xenial now and then we can look at the SRU for this. Can you update the bug to add the template?20:35
stgrabercyphermox: sure, I'll add a testcase once we have it in xenial and working20:36
stgrabercyphermox: I was going to SRU the ugly lxc workaround but if we can get network-manager fixed itself, even better20:36
=== salem_ is now known as _salem
chilukslangasek: I know you are busy, but can I get an upload for nfs-utils done for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509120  I have a feeling it will look familiar to you.21:02
ubottuLaunchpad bug 1509120 in nfs-utils (Ubuntu) "Process accounting deadlock with idmapd callout when writing to NFSv4 mount" [Medium,In progress]21:02
slangasekchiluk: oh hah, is that really just a keyutils upcall bug?21:09
cyphermoxstgraber: yeah, feel free to not SRU your ugly lxc fix now if this NM update works :)21:14
stgrabercyphermox: already reverted it in xenial, it's clearly not something I wanted to have to keep around :)21:15
chilukslangasek: yes it is.21:19
slangasekchiluk: I notice the rationale for adding the dependency in vivid+ was that this is required for systemd compatibility, because in the systemd case everything assumes we only use /usr/sbin/nfsidmap as an upcall *instead* of running idmapd (/etc/request-key.d/id_resolver.conf).  So this certainly seems to be a workaround rather than a proper fix21:20
slangasekdo I have that right?21:20
chilukslangasek: it's not a workaround when communicating with old nfsv4 servers that don't support sec=sys, and thus aren't using idmapd.21:23
chilukafaik.. but I wouldn't consider myself an nfs expert by any stretch of the imagination21:24
slangasekshould anyone? ;)21:24
chilukwe were only able to rerpoduce the hang by using an ancient 2.6.32 centos machine21:24
chilukprecisely because sec=sys isn't supported by such an ancient kernel.21:24
slangasekdo you know what the RPC is that triggers this path, vs. working via idmapd?21:24
chilukI don't.21:25
chilukI could tcpdump it real quick if you'd like.21:25
chilukslangasek: ^^21:25
slangasekchiluk: hit me21:25
chilukdon't tempt me...21:26
slangasekchiluk: has this been reproduced cross-architecture?21:26
slangasekchiluk: because my next question is, is it reproducible with the 14.04.0 kernel or only with hwe-v?21:27
chilukyeah ppc is hitting it although I don't have a trustable backtrace yet from them, and I'm seeing it on x86_6421:27
chilukoh no, I'm using 3.13.21:27
chilukdo you still want that tcpdump?  I just realized that the machine will become unusable once I instantiate the crash.. so we'll see what kind of messages actually can get logged.21:28
chiluknm I can capture from the server.21:29
slangasekchiluk: I think I'm happy without the tcpdump21:30
chilukslangasek, yeah .. I was a bit curious myself about the rejected rpc call.21:30
Unit193FWIW, Debian 786690 still affects wily.21:49
ubottuDebian bug 786690 in pbuilder "pdebuild fails to builds package with dpkg-dev 1.18.0 (dpkg-buildpackage -S failing with missing build-deps)" [Important,Fixed] http://bugs.debian.org/78669021:49
xnoxi'm blinking over "1TB PCIe Solid State Drive" whilst starring at XPS 15 (9550).22:59
sarnoldchrisccoulson: ^^^23:00
xnoxthe new XPS 15, however so far it's with windows only, and i don't see a developer edition with ubuntu yet.23:00
xnoxsuperm1: is XPS 15 (9550) pre-orderable as a developer edition? i shall give them a call tomorrow.23:01
sil2100doko: so, to continue on the ocaml transition I need multiple arm64 binaries built from the dependency level 3 uploads I made, meaning I'm currently stalled on that23:05
sil2100But tomorrow at least some of them should be available, so I can continue from there then23:05
superm1xnox: not currently. It's a work in progress still.23:07
superm1danjared: will know current status better than I23:07
cjwatsonsil2100: yeah, for that number it's sensible just to wait - at least the ocaml stack isn't too deep23:09
cjwatsonthe queue's "only" an hour long at the moment23:09
danjaredwhat'd I do?23:41
danjaredxnox: no, no current plans for an Ubuntu version of the XPS 15. there are plans for the Precision Mobile 551023:42

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