/srv/irclogs.ubuntu.com/2016/05/04/#ubuntu-devel.txt

smoserpitti, around ?03:14
smoseri think i relize the issue with letting the udevrule go through.03:15
smosercloud-init wont have written the .link file to rename at the point when the udev rule processes the .link03:15
smoserso cloud-init local *will* have to re-trigger or otherwise have the systemd.link stuff fire again03:16
smoserhow were you re-triggering with udev to get the .links processed ?03:19
cyphermoxcjwatson: yes, will SRU. thanks. I was looking hard at base-installer, not at apt-setup :/03:23
cyphermoxor at least, not at that part of base-installer that has apt-setup keys.03:23
cyphermoxbetween us we might manage to really fix the overlay code.03:23
smoserpitti, 'udevadm test-builtin net_setup_link /sys/class/net/ens4' works to show that the cloud-init written .link files do the right thing.03:35
smoserbut i think i have to re-send the hotplug event to get it renamed.03:35
=== hikiko is now known as hikiko|off
=== athairus is now known as afkthairus
CarlFKhttps://help.ubuntu.com/lts/installation-guide/armhf/apbs04.html#preseed-apt   how do I get it to not #comment out deb-src  lines?  (new in xenial)07:08
zygagood morning07:25
tjaaltonwgrant: still around? I sent a soyuz question (#293230) about bumping the size of ppa:canonical-x/x-staging, llvm is taking all the space preparing next lts stack :)08:14
wgranthow on earth08:15
wgrantIt's already 8GiB!08:15
* wgrant doubles08:15
tjaaltonllvm is big08:15
tjaaltonthanks!08:15
mwhudsonis there a script for doing the Maintainers: Ubuntu Developers, XSBC-Original-Maintainers: thing?08:24
Laneymwhudson: updata-maintainer08:24
Laneywith spelling that is good08:24
mwhudsonLaney: thanks08:26
mwhudsonoh wow, python, i was expecting perl :-)08:27
Laneyit was probably written this decade :P08:27
=== davmor2_ is now known as davmor2
zygahey mwhudson08:45
cjwatsonCarlFK: d-i apt-setup/enable-source-repositories boolean true09:03
=== marcusto_ is now known as marcustomlinson
sil2100mvo: hey! Is it ok for me to release the currently staged changes in livecd-rootfs to yakkety?10:51
sil2100mvo: I have some of my changes that we'd need released to unblock image builds10:51
=== xavigarcia is now known as xavigarcia_lunch
mvosil2100: yeah, thats fine10:59
mvosil2100: ogra_ also has some pending changes11:00
sil2100Thanks!11:00
ogra_mvo, oh, didnt you say you pushed them to trunk ?11:00
sil2100They're pushed to trunk but not released yet11:00
sil2100I'm releasing trunk right now if that's ok11:00
ogra_bah, i just upgraded my phone to tonights rc-proposed image ... no apps in the apps scope ... no matter how often i refresh11:01
ogra_ok, seems ten times is the charm ...11:01
=== xavigarcia_lunch is now known as xavigarcia
yofeldoko: did you intentionally drop the multiarch changes from libical?12:09
dokoyofel, no, saw too late that they were only applied in experimental12:11
dokobut I didn't check if we can sync the experimental package12:11
dokoso maybe I better restore these12:11
yofelwould be nice, it's causing build failures in some kde autopktests as cmake hardcodes the lib path in some places12:12
dokoahh, I remember12:15
dokobreakfast first12:16
yofeldoko: and thanks for merging digikam12:17
alexbligh1Is this the sort of thing you'd take a 14.04 SRU for (assuming my one character patch to fix it is OK): https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/157818512:22
ubottuLaunchpad bug 1578185 in nbd (Ubuntu) "nbd-client 3.7 connects read-only to newer nbd servers" [Undecided,New]12:22
smoseralexbligh1, if if it doesn't break working with older nbd servers' it would surely seem appropriate for sru from what that bug says.12:23
alexbligh1smoser, nope, it doesn't break anything. OK, I will persuade Wouter (Debian maintainer and nbd maintainer) my one line patch is a good plan :-)12:24
alexbligh1smoser, thx12:24
shadeslayerchrisccoulson: hi, I was wondering if you had a moment to talk about firefox? I seem to be hitting a race condition when the configure step is a bit too slow12:39
shadeslayerfor eg. on armhf12:39
rbasakalexbligh1: thank you for looking after this. Let me know if you need any help with sponsorship etc.12:40
shadeslayerchrisccoulson: I was wondering if you had seen something similar?12:40
alexbligh1rbasak, thx - if you could tell me how to mark it as 14.04 only that would be great.12:40
rbasakalexbligh1: is it Fix Released in Yakkety then? I can add the Trusty task for you. AIUI, that was ACL-restricted to uploaders and triagers only because people kept misunderstanding the purpose or something.12:42
rbasakalexbligh1: done12:42
alexbligh1rbasak, yes it was fixed in wily when 3.10 was imported. Thanks.12:43
=== _salem is now known as salem_
roadmrhey folks! so on xenial I get an "updates available" bubble but it's not actionable. Clicking on it does nothing, nor does the dancing update manager appar in the unity dash. I had to hunt it down manually. Is this a bug?13:12
sergiusenscjwatson pitti hello again, is the fact that I need to do this https://github.com/ubuntu-core/snapcraft/pull/499/files for yakkety a bug in snapcraft that went unnoticed (worked all through xenial) or the new apt/python-apt in yakkety?13:22
cjwatsonsergiusens: Don't know, I'm afraid13:40
ginggspitti: hi, can something be done about compute's ppc64el test failure blocking nvidia-cuda-toolkit please? From what I can see, nvidia-cuda-toolkit provides an alternate build-depends which isn't even being tested. The failures have been since the switch to boost1.60.14:03
coreycbbdmurray, arges: Hi, any chacne we could get a review for the liberty point release in bug 1569502 ?14:14
ubottubug 1569502 in nova (Ubuntu Wily) "[SRU] liberty point releases" [Undecided,Confirmed] https://launchpad.net/bugs/156950214:14
pittiginggs: I added a compute/ppc64el ignore hint14:18
ginggspitti: danke!14:19
rbasak"dpkg: dependency problems prevent processing triggers for ufw"14:32
rbasakIs this an apt bug? I don't see an obvious packaging deficiency or opportunity for there to be a dependency loop.14:32
rbasakhttp://paste.ubuntu.com/16218132/ is my reproduction of bug 157117414:33
ubottubug 1571174 in squid3 (Ubuntu) "package squid3 failed to install/upgrade: dependency problems - leaving triggers unprocessed" [High,Confirmed] https://launchpad.net/bugs/157117414:33
rbasakIt seems to me that apt should have chosen to configure python3 first.14:35
argescoreycb: i got it15:24
pittircj: cat /sys/class/tty/console/active15:31
rcjpitti, thanks15:31
dokoyofel, https://bugs.launchpad.net/ubuntu/+source/ffmpegthumbs/+bug/1578269 (only recommended by digikam)15:38
ubottuLaunchpad bug 1578269 in ffmpegthumbs (Ubuntu) "demote ffmpegthumbs to proposed, fails to build with new ffmpeg" [Undecided,Confirmed]15:38
cjwatsondoko: why do you disable entire test suites rather than just the failing test?  (survex, which I'd just started to look at upon noticing that you'd sledgehammered it)16:07
dokocjwatson, sure, I could have done this as well. however I didn't see any failure on the local build16:13
tjaaltondoko: arm64 fails to build llvm-3.8 on trusty, log says "internal compiler error". this probably is a blocker for lts-xenial. should I file a bug against gcc-4.8?16:13
dokotjaalton, I'm not involved with the lts uploads of clang. does this persist when you give it back?16:14
tjaaltondoko: built it on a ppa, haven't tried rebuilding16:15
tjaaltonwill do that now16:15
dokocjwatson, alsa-plugins-extra is also merged16:17
cjwatsondoko: I don't see any failure right now on the local build either (I'm investigating), but the point of a test suite is to make problems on future builds less likely16:17
dokocjwatson, right, that's why I filed a bug report which I intend to re-open after the current transitions16:18
cjwatsonIME those bug reports get lost16:19
dokook, then I'll re-upload after the transition with the fix reverted16:21
cjwatsonwell like I say I was working on them anyway ...16:22
dokoI only worked on these while you were bringing you kids to bed last night, and just re-started again. but it's not just ffmpeg which is blocking16:23
cjwatsonvalgrind shows what the survex problem probably is16:26
cjwatsonand the freshplayerplugin problem is easily reproducible locally in a UTF-8 locale16:30
hallynpitti: is there a 'dh_systemd_disable' sort of thing?16:31
pittihallyn: there isn't, what should that do?16:32
pittiunits are disabled by default, after all16:32
hallynpitti: problem is, we currently have libvirt-bin.service, which is Alias=libvirtd.  We're switching to debian packaging, which has libvirtd.service instead16:32
hallynWhich I want to Alias=libvirt-bin for ahwile probably16:33
hallynbut how should i do the renaming?16:33
hallyn(sorry, biam)16:33
pittihallyn: ah, so you need to rename the enablement symlinks in the prerm?16:33
pittierr, preinst16:33
pittihallyn: I think this would be a conditionalized mv in the preinst16:33
cjwatsondoko: When you said "Revert last change" in freshplayerplugin (presumably the build-dependency on libjack-dev), you don't seem to have actually done so.  Should I do so since I plan to upload it anyway?16:38
hallynpitti: so i should do it manually using 'mv'?16:41
pittihallyn: I think that's better than just rm'ing it and re-creating the new ones, if you want to maintain the fact that an admin manually disabled it16:42
pittii. e. it should still be disabled after the upgrade16:43
hallynpitti: yeah right now i was just trying to stop it (as in https://git.launchpad.net/~libvirt-maintainers/ubuntu/+source/libvirt/tree/debian/libvirt-daemon-system.preinst?h=2016-05-02/yakkety) and i manually tried 'disabling' it, but that didn't suffice16:45
hallyni'll try moving the files - then do i do a systemctl reload?  (from inside prerm?)16:45
cjwatsondoko: Seems to make no difference to the configuration, so I'll go ahead and do that16:45
hallyn(of course, i *could* just punt on this and keep this as delta from debian, but i'd really like to minimize that)16:46
cjwatsondoko: freshplayerplugin and survex both fixed16:56
dokota \o/16:56
tjaaltondoko: rebuild fails too16:56
cjwatsonand uploading an ffmpeg patch that's supposed to fix the autopkgtest failure17:01
hallynpitti: gonna try http://paste.ubuntu.com/16221711/17:06
pittihallyn: looks good at first sight, and also gets rid of the bare systemctl invocation (which breaks under upstart and with policy-rc.d in e. g. chroots)17:08
pittihallyn: FTR, if you ever have that case, please use deb-systemd-invoke, this checks policy-rc.d17:09
pittior just invoke-rc.d17:09
hallynpitti: ok, thx17:10
hallynactually, lemme think.  we have cloud archives, so in fact what i have in that paste is not sufficent,17:10
hallynas it'll break if someone in 14.04 upgrades to it17:11
hallyni don't suppose we can hae any sort of sanity guarantees about lts-to-lts upgrades even with cloud archives?17:11
hallynjamespage: ^ is there going to be a cloud archive providing yakkety's libvirt to pre-15.10 users?17:11
hallyn(i..e non-systemd-based)17:11
hallynzul: ^17:12
zulhallyn: dunno yet :)17:14
hallynwell maybe i'll just leave it broken until we know17:14
hallynbc 'fixing' it also means papering over other potential bugs17:14
hallynpitti: so instead of checking for that symlink by hand should i be doing 'deb-systemd-invoke systemctl is_enabled libvirt-bin' ?17:15
hallynnah17:16
pittihallyn: deb-systemd-invoke is just for start/stop; enable/disable is fine, not a thing that policy-rc.d covers17:16
pittihallyn: but it's by and large the same as checking for the symlink directly, so mostly a matter of preference I'd say17:16
hallynok - thanks17:17
pittihallyn: actually17:17
pittihallyn: deb-systemd-helper has is-enabled, enable, disable etc., and that might be better as /var/lib/systemd/deb-systemd-helper-enabled/ also needs to be updated17:18
pittithat's the crazy Debian thing to sync enablement over upgrades, across init systems etc.17:18
pittithis might fire back if we don't update this too17:19
hallynugh17:19
pittihallyn: sorry, I think that might be the first time this kind of upgrade issue happens17:19
hallynbut what about renames?17:19
hallynthat is deb-systemd-helper enable/disable isn't quite enough...  oh, but17:20
dokowgrant, cjwatson, pitti: https://launchpadlibrarian.net/257883350/buildlog_ubuntu-yakkety-i386.slurm-llnl_15.08.10-1build1_BUILDING.txt.gz (packages modifying -dbgsym packages).  is there a plan when we'll switch to the new dbgsym packages?17:20
hallyni can just disable, move the classical links by hand, then enable?17:20
hallynpitti: put another way: what the heck is under /var/lib/systemd/deb-systemd-helper-enabled/17:20
pittihallyn: so I think "if deb-system-helper is-enabled <old name> then disable the old name, otherwise disable the new name17:20
pittihallyn: so, I'm fairly sure that just handling the links as you do it now should work17:21
pittias the /var/lib/helper stuff never trumps admin changes17:21
pittiso, forget what I said17:21
hallynok17:21
pittihallyn: the stuff in /var/lib basically tracks the distro defaults17:22
hallynotherwise i was thinking i'd need to deb-systemd-helper purge; move the files, deb-systemd-helper enable17:22
hallynok - so those files should get dropped naturally?17:22
hallyni'll make a note to check them in a test - thanks pt17:22
hallynuh.  thanks pitti17:22
pittithis would be really ugly indeed17:22
pittihallyn: for testing, I think check that it upgrades correctly with an enabled and disabled service, and that installing it again works17:23
pittiand ignore the /var stuff17:23
hallynok thx17:23
=== afkthairus is now known as athairus
hallynman sometimes ppas just take forever to publish after building...17:55
dokoubuntu-keyboard-swedish/amd64 unsatisfiable Depends: hunspell-sv-se17:57
dokoubuntu-keyboard-swedish/armhf unsatisfiable Depends: hunspell-sv-se17:57
dokoubuntu-keyboard-swedish/i386 unsatisfiable Depends: hunspell-sv-se17:57
dokosil2100, ^^^17:57
hallynpitti: argh.  well i can't do that in pre-inst, apparently /lib/systemd/system/libvirt-bin.service has been removed by this point18:18
pittihallyn: uh? that sounds wrong; preinst runs before unpack18:18
hallynmaybe i do it in the libvirt-bin (which is otherwise just a metapackage) preinst/18:18
pittino, you can't rely on the unpack order then18:19
hallynpitti: yeah but the libvirtd.service is in libvirt-daemon-system package;  libvirt-bin.servce is in libvirt-bin package18:19
hallynso what to do?18:19
pittioh18:19
pittihallyn: does one depend on the other?18:20
hallynyeah libvirt-bin depends on libvirt-daemon-system18:20
hallynso, maybe it would be easier to keep libvirt-bin.service for now, and do that switch after we've gotten rid of the libvirt-bin package altogether?18:22
hallynso the move is at least happening within one pkg?18:22
pittihallyn: so you need to do it in the package which originally shipped the old name18:22
hallynok,18:22
pittiif that was libvirt-bin, its preinst needs to do that, yes18:22
pittieven if it's empty afterwards18:22
hallyni can do that.  bu ti'm still worried about the file being gone,18:23
pittibut you need that empty package for upgrades anyway18:23
hallynbecause at postinst time for libvirt-daemon-ssytem it still says that libvirt-bin.service exists18:23
hallynso is that getting cached under /var/lib somewhere during package remove/unpack?18:23
hallynall right so lemme try with that in libvirt-bin.preinst.  thx18:26
pittihallyn: dependencies get configured before postinst runs; deb contents does not get cached, now18:26
pitti(sorry, distracted, sprint)18:26
hallynpitti: hold on.  there is existing code there from debian's transition.  i was misreading that and thinking it was my code from an earlier upstart->systemd xition18:27
hallynso actually mayb ei just need to tweak the version numbers there and it'll just work18:28
hallynpitti: in particular, http://paste.ubuntu.com/16223586/18:28
hallyndoes that look like it would work?18:28
* hallyn tries18:29
pittihallyn: that actually looks fairly good, yes18:31
hallyncool let's see if it works18:31
pittihallyn: it doesn't maintain admin changes, though18:31
pittihallyn: i. e. if the admin manually disabled the service, it will restart after the upgrade18:32
hallynhm18:32
hallynand i can only check that from libvirt-bin.preinst?18:32
hallynno, not if i use the deb-systemd helpers18:33
hallynso to that hunk i could add a tmpfile created if the service is enabled, and only enable it by hand...18:34
hallynpitti: by disabled you mean stopped or actually disabled so it won't start again?18:34
pittihallyn: disabled (stopped is fine)18:34
hallynsigh18:36
hallynall right i'll test it both ways.  thx18:36
hallynpitti: meh, that doesn't work. I still get http://paste.ubuntu.com/16224784/19:22
hallynso i'll do it my way in libvirt-bin.preinst19:22
hallynmy way -> your way?  but not debian's way :)19:22
dokoroaksoax, please could you have a look at https://launchpad.net/ubuntu/+source/virtualbox/5.0.20-dfsg-1/+build/9669239 ? currently blocking some transitions19:49
roaksoaxdoko: ???? I've never touched virtualbox i dont think ...19:55
dokoohh, looked at the wrong package19:56
roaksoax:)19:58
cjwatsondoko: There is no current plan, nor am I even sure it's agreed that we will switch.20:25
cjwatsonThe way that ended up in Debian is significantly less convenient to deal with for no obvious advantage, although the delta is awkward.20:26
dokoI should propose for debian policy not to modify dbgsym packages ...20:28
pitticjwatson: we could make the delta a bit smaller by patching debhelper to name them .ddeb instead of .deb; in theory this should then not need LP changes, or am I missing something?20:29
hallynpitti: nope, that (manual mv'ing in libvirt-bin.preinst) didn't work.  i'll use the deb-systemd-helper to disable and leave tmpfiles for postinst to know whether to reenable20:31
hallynugh20:31
cjwatsonpitti: Not sure.  There's all the hairy stuff that arranges to control whether ddebs are built on an archive-by-archive basis20:33
cjwatsonBuild-Debug-Symbols etc.20:33
pitticjwatson: oh, the parsing of /CurrentlyBuilding etc.20:33
hallynoh great, this is helpful for testing:20:38
hallyndeb-systemd-helper is-enabled libvirt-bin.service20:38
hallyn/usr/bin/deb-systemd-helper was not called from dpkg. Exiting.20:38
* hallyn needs more info on deb-systemd-helper mask/unmask20:45
dokoAlbertA: please could you have a look at https://bugs.launchpad.net/ubuntu/+source/mir/+bug/157838120:51
ubottuLaunchpad bug 1578381 in mir (Ubuntu) "mir tests fail in yakkety on amd64 and i386" [Critical,Confirmed]20:51
AlbertAdoko: 0.21? shouldn't it be 0.22?20:52
dokoAlbertA, there is no 0.22 in https://launchpad.net/ubuntu/+source/mir20:54
AlbertAcamako: bregma: ^20:55
AlbertAdoko: I thought the ci-train was supposed to release to the transitional overlay thingy20:55
dokoAlbertA, it's my understanding that this is not yet in effect for yakkety20:56
AlbertAdoko: in any case, the test failures look intermittent:20:56
AlbertA[ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency20:56
AlbertAI think that test will potentially fail if there's too much load on the build machines20:56
dokoAlbertA, I can give them back and see what happens. can you save a copy of the build log locally?20:56
AlbertAif you re-run the builds it will most likely be ok20:58
=== salem_ is now known as _salem
dokoAlbertA, give back succeeded. closing the issue. ta21:41
AlbertAdoku: ack21:42
camakoAlbertA, mir 0.22 is not in xenial either21:43
camakoweird21:43
camakoor meybe expected due to the overlay21:44
roaksoax821:59
pittiinfinity: FYI, just committed bug 1577966, so happy proxying (if you run autopkgtest from git, like all the kool kids do :) )22:08
ubottubug 1577966 in autopkgtest (Ubuntu) "automatically setup proxies other than apt-cacher-ng" [Undecided,Fix committed] https://launchpad.net/bugs/157796622:08

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