wxlcyphermox: good to hear from you. there were some interesting tracebacks as recent comments on the bug report.00:10
slangasektsimonq2: so how and why is bug #1647031 affecting you, given that libnss-resolve is in ubuntu-standard and masks the issue?00:52
ubot5`bug 1647031 in systemd (Ubuntu) "systemd-resolved’s server does not follow CNAME records" [Low,Triaged] https://launchpad.net/bugs/164703100:52
tsimonq2slangasek: I still get the issue when that is installed afair00:57
slangasektsimonq2: "AFAIR"> would be good to have confirmation, since that conflicts the information on the bug00:57
tsimonq2slangasek: OK, I'll let you know on Thursday when I have access to that install again00:58
Mirvplease remove these (unbuildable, related to the upstart removals) s390x binaries from zesty: libqt5purchasing5 qml-module-qtpurchasing qtpurchasing5-dbg qtpurchasing5-dev-dbgsym libqt5purchasing5-dbgsym qml-module-qtpurchasing-dbgsym qtpurchasing5-dev08:00
Mirvfiled bug #1653906 about it08:17
ubot5`bug 1653906 in qtpurchasing-opensource-src (Ubuntu) "RM: s390x binaries of qtpurchasing-opensource-src" [Undecided,New] https://launchpad.net/bugs/165390608:17
ginggsmorning! would someone please 'force-badtest ocrmypdf/4.2.5-1/s390x' ?  debian bug #84909409:06
ubot5`Debian bug 849094 in liblept5 "liblept5: Broken on s390x (+ other big endian archs)" [Normal,Open] http://bugs.debian.org/84909409:06
ginggstumbleweed, if you're in a compatible timezone ^11:11
apwginggs, why would we want to break that on s390x by letting it migrate?  it worked before11:14
ginggsapw, my understanding is it was always broken on big-endian, the new tests are exposing the problem11:15
apwahh ok11:16
apwginggs, and done11:34
ginggsapw: thanks!11:35
=== marcusto_ is now known as marcustomlinson
cjwatsonCan somebody remove the force-badtest openssh from the britney hints branch?  It passes everywhere now.12:17
cjwatson(It's in pitti's hints file, but I don't think he has commit access any more?)12:17
* apw has a look12:17
apwcjwatson, and done12:19
cjwatsonTook about a week of on and off arm's-length debugging ...12:19
apwthat sounds like a lot of a nightmare12:20
cjwatsonA bit.  Should be suitably nailed to the wall now anyway :)12:20
-queuebot:#ubuntu-release- Unapproved: libica (yakkety-proposed/universe) [2.6.1-3 => 2.6.1-3ubuntu0.1] (no packageset)12:33
-queuebot:#ubuntu-release- Unapproved: libica (xenial-proposed/universe) [2.6.1-1ubuntu2 => 2.6.1-1ubuntu2.1] (no packageset)12:37
flocculantrelease team peoples - are you aware the daily boots direct to the desktop? bug 165171612:44
ubot5`bug 1651716 in ubiquity (Ubuntu) "17.04 boots direct to live desktop, no option to Try or Install" [Undecided,Confirmed] https://launchpad.net/bugs/165171612:44
mdeslaurcould someone please remove bubblewrap from the yakkety upload queue, I need to rebuild it in the security pocket instead12:56
apwmdeslaur, bubblewrap (source)12:57
apwthat one ?12:57
mdeslaurapw: yep12:57
apwmdeslaur, and gone12:57
mdeslaurthanks apw12:57
-queuebot:#ubuntu-release- Unapproved: rejected bubblewrap [source] (yakkety-proposed) [0.1.5-1~ubuntu16.10.0]12:58
=== marcusto_ is now known as marcustomlinson
ginggsapw: do we need 'force-badtest ocrmypdf/4.3.4-2/s390x' as well for the new version?13:41
apwginggs, looks to be ignored for example for leptonlib, what are you waiting on13:44
apwginggs, oh ocrmypdf is actually waiting to migrate, derp13:44
ginggsapw: sorry i didn't realize you needed to do that per version, i thought it was worked like >= 4.2.5-113:53
apwginggs, some of them do, some not.13:56
tumbleweedginggs: you can do all versions, but then it's easily forgotten15:34
Mirvcould an archive admin bug handle bug #1653906 so that my ticket rebuild qtpurchasing (https://bileto.ubuntu.com/#/ticket/1985) wouldn't show a missing build? (since it's not really missing, as the s390x binaries could not be built in zesty if a rebuild was done anymore, regardless of the landing)16:20
ubot5`bug 1653906 in qtpurchasing-opensource-src (Ubuntu) "RM: s390x binaries of qtpurchasing-opensource-src" [Undecided,New] https://launchpad.net/bugs/165390616:20
infinityMirv: Err, why are we still doing upstart-related removals?  Didn't xnox put in a bunch of work to make things stop depending on upstart?16:55
Mirvinfinity: probably because the upstart problems need to be fixed all at once. right now libpay2 is unavailable on s390x due to manual stop gap dependency in it, so qtpurchasing can't rebuild on s390x. I think xnox will eventually need to have a single huge silo that removes all upstart dependencies, both actual and the made up ones that were inserted in various points to keep touch stack landable for16:57
Mirvthe last four months.16:57
Mirvsince doing it partially probably would introduce a chain reaction16:58
infinityAnd this removal here was probably one that was missed when people did this crap in yakkety.16:58
infinity(And yes, "crap" sums up how I feel about the upstart/s390x "solution")16:59
infinityAlright, I'll poke at this bug.16:59
Mirvyes, it's pretty crap crap16:59
infinityMirv: Done.17:03
Mirvthank you17:09
tsimonq2bubblewrap, heh17:21
tsimonq2Are there docs somewhere showing what exactly is done when a new development release is being formulated? On the release schedule it says "Toolchain Uploaded" and the appropriate wiki page just talks about the various parts of the toolchain, but not actually what it means to have "Toolchain Uploaded"17:26
tsimonq2I'm just curious, as I'm not finding it documented anywhere.17:26
tsimonq2Like, inspecting zesty-changes shows some things like setting Zesty as the release etc. but not actually what happens when new releases are a thing.17:27
cjwatsontsimonq2: https://wiki.ubuntu.com/NewReleaseCycleProcess17:31
tsimonq2cjwatson: Ooh, fancy, thanks.17:35
tsimonq2One other thing, why does Lintian *still* not recognize zesty as a release? Should I file a bug, or is that something someone forgot about that I can just submit a debdiff for?17:36
-queuebot:#ubuntu-release- Unapproved: lxc (trusty-proposed/main) [2.0.6-0ubuntu1~ubuntu14.04.1 => 1.0.9-0ubuntu2] (ubuntu-server)17:40
cjwatsonhow about I just use my upstream commit bit to fix that in Debian17:40
tsimonq2cjwatson: Yes please. :)17:42
cjwatsonhttps://anonscm.debian.org/cgit/lintian/lintian.git/commit/?id=0170df01277e46b618c269de0a0622389c573a39 - it's probably OK to just let that be synced later, but feel free to cherry-pick if you're in a rush17:45
tsimonq2...maybe if I had upload access I would have that option :P17:47
tsimonq2cjwatson: But thanks :)17:48
tsimonq2!info lintian zesty17:50
ubot5`lintian (source: lintian): Debian package checker. In component main, is optional. Version 2.5.50 (zesty), package size 792 kB, installed size 3831 kB17:50
tsimonq2!info lintian unstable17:50
ubot5`lintian (source: lintian): Debian package checker. In component main, is optional. Version 2.5.50 (unstable), package size 1019 kB, installed size 3831 kB17:50
tsimonq2Ah ok.17:50
tsimonq2...why would the package size in unstable be larger than in Ubuntu?17:50
stgraberinfinity: can you let that lxc upload into trusty-proposed pretty please? that should fix the autopkgtest failure we've had so far by having our test detect busted kernels properly17:51
cjwatsontsimonq2: stripped upstream changelog17:56
cjwatson$ diff -u <(zcat unstable/usr/share/doc/lintian/changelog.gz) <(zcat zesty/usr/share/doc/lintian/changelog.gz) | diffstat17:56
infinitystgraber: Hahaha.  I was just looking at that.17:56
cjwatson 62 |17741 ---------------------------------------------------------------------17:56
cjwatson 1 file changed, 1 insertion(+), 17740 deletions(-)17:57
infinitystgraber: (The failure, not your upload)17:57
infinitystgraber: Oh.  Different (maybe?) failure.17:58
infinitystgraber: Care to have a glance at https://bugs.launchpad.net/auto-package-testing/+bug/1654025 and see if you can make sense of it?17:58
ubot5`Ubuntu bug 1654025 in Auto Package Testing "trusty/armhf dkms tests are killing workers" [Undecided,New]17:58
infinitystgraber: As for this lxc upload... Skipping a test doesn't seem to resolve the bug?18:00
infinitystgraber: Unless the feature being tested also will refuse to be used on old kernels.18:01
stgraberinfinity: LXC does fail when it runs into that particular kernel issue, it's said LXC failure which was then causing autopkgtest to fail. So we now detect it ahead of time and skip the test rather than failing when we get the error.18:01
stgraberinfinity: it's not ideal in that there's still a kernel bug, but it's limited to the 3.13 kernel and hasn't seen much traction in getting fixed18:02
infinitystgraber: And this bug/interaction has always existed in trusty lxc-versus-3.13?18:02
infinitystgraber: As in, no new regression here, just a test that exposed it?18:02
stgraberinfinity: LXC used to go ahead with the busted-ness which was enough to make the test happy and then break people randomly. LXC 1.0.9 detects the kernel being busted and refuses to have anything to do with it.18:03
infinitystgraber: Okay, that sounds like progress, even.  (not ideal progress, but progress nonetheless)18:03
infinitystgraber: So, accepting that.18:04
stgraberhttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507463 is the underlying issue I believe18:04
ubot5`Ubuntu bug 1507463 in linux (Ubuntu) "OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13" [Medium,Confirmed]18:04
-queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (trusty-proposed) [1.0.9-0ubuntu2]18:04
infinitystgraber: Can you look at the bug above (specifically, Laney's strace vomit) and tell me if that rings any bells?18:04
infinitystgraber: It looks suspiciously container/namespace related, and I can't reproduce in a plain old chroot.18:04
stgraberinfinity: so it's apt-get source dkms on trusty blowing up somehow?18:06
infinity"apt-get source -q --only-source nvidia-graphics-drivers-340=340.98-0ubuntu0.14.04.1" is the call, and yeah, in a chroot, it just does a thing, downloads some source, prints to stdout, life is good.18:07
infinitystgraber: In a container, it appears to not do a useful thing. :P18:07
infinity(Though still exits 0, thanks apt)18:08
LaneyBit weirder18:08
LaneyIt exits 0 but the rest of the script doesn't run18:08
infinityLaney: That's the script's fault, surely.18:08
infinityLaney: But the apt failure it the curious bit right now.18:08
LaneyI think the whole script is being killed18:09
LaneyBut yeah, surely fixing that will fix whatever it is18:09
infinityLaney: The script being "killed" is by design, surely.18:09
infinityLaney: It's logging an error, and even gives us the error.18:10
infinity(The error being that apt exited without printing anything to stdout, and we're pretty uncool with that)18:10
LaneyThe script is meant to catch the bad exit code, look at the output and then exit with it18:10
LaneyWe should see that happening, given set -x18:10
stgraberLaney: any chance you can get a dmesg output post failure?18:11
stgraberthe first thing that comes to mind with such behavior (command just stopping halfway through whatever it's doing) would be the kernel oom killer18:11
stgraberthough that usually causes a non-zero exit :)18:12
infinityOOM kills return a 9, not 0.18:12
Laney'fraid I've got to get out of here for a bit18:12
stgraberI'll try to reproduce this on my m400 (xenial arm64 host), should be as close as I can get18:14
LaneyI'm just running it on my desktop (zesty, amd64)18:15
stgraberinfinity: we've seen the kernel do weird shit when the oom is cgroup triggered :)18:15
LaneyWe just get it on armhf for autopkgtest because that's the only place we use lxd18:15
stgraberLaney: oh, fun18:15
infinityWe use it on s390x too.18:15
infinityBut it might not be triggering the same tests.18:15
stgrabernot on trusty though18:16
infinityOh, and trusty.  Yeah.18:16
stgraberrunning "apt-get source --only-source nvidia-graphics-drivers-340" in a trusty container here doesn't reproduce the issue though18:16
stgraberLaney: do you have a reproducer that doesn't involve running all of autopkgtest with the lxd backend?18:16
LaneyNope, sorry18:17
infinityOdds are it's just that one command.18:17
infinityBut I don't lxd well enough to tell you that. :P18:17
LaneyI think I tried earlier in a normally started container (but still an autopkgtest one) and it worked18:18
LaneyThe desktop is off now because of the aforementioned leaving18:18
stgraberLaney: does autopkgtest with the lxd backend exec stuff through "lxc exec" or through ssh?18:22
stgraberI just tried a simple shell script which runs the apt-get source command and then prints something in both of "lxc exec"'s modes and both worked fine18:23
infinityDefine working fine.  Does it download the source?18:24
stgraberdownloads and unpacks18:26
infinityWell, that's irksome.18:28
infinityssh certainly could be involved, if it's mimicking the xen and kvm workflows.18:29
tsimonq2cjwatson: Hmmmm ok thanks18:35
-queuebot:#ubuntu-release- New binary: gyoto [s390x] (zesty-proposed/universe) [1.2.0-2ubuntu1] (no packageset)19:22
-queuebot:#ubuntu-release- New binary: gyoto [ppc64el] (zesty-proposed/universe) [1.2.0-2ubuntu1] (no packageset)19:24
-queuebot:#ubuntu-release- New binary: gyoto [amd64] (zesty-proposed/universe) [1.2.0-2ubuntu1] (no packageset)19:29
-queuebot:#ubuntu-release- New binary: gyoto [powerpc] (zesty-proposed/universe) [1.2.0-2ubuntu1] (no packageset)19:32
-queuebot:#ubuntu-release- New binary: gyoto [i386] (zesty-proposed/universe) [1.2.0-2ubuntu1] (no packageset)19:34
-queuebot:#ubuntu-release- New binary: gyoto [arm64] (zesty-proposed/universe) [1.2.0-2ubuntu1] (no packageset)19:51
-queuebot:#ubuntu-release- New binary: gyoto [armhf] (zesty-proposed/universe) [1.2.0-2ubuntu1] (no packageset)19:57
* tsimonq2 throws bug 1647031 at barry 20:37
ubot5`bug 1647031 in systemd (Ubuntu) "systemd-resolved’s server does not follow CNAME records" [Low,Triaged] https://launchpad.net/bugs/164703120:37
tsimonq2May be relevant... :)20:37
tsimonq2(can't respond to the email atm)20:37
-queuebot:#ubuntu-release- Unapproved: rejected owncloud-client [source] (yakkety-proposed) [2.2.2+dfsg-1ubuntu0.2]20:48
Laneystgraber: I think https://git.launchpad.net/~ubuntu-release/autopkgtest/+git/autopkgtest/tree/virt/autopkgtest-virt-lxd#n149 that beauty is prefixed to commands to run20:50
-queuebot:#ubuntu-release- Unapproved: owncloud-client (yakkety-proposed/universe) [2.2.2+dfsg-1ubuntu0.1 => 2.2.2+dfsg-1ubuntu0.2] (no packageset)20:54
-queuebot:#ubuntu-release- Unapproved: accepted owncloud-client [source] (yakkety-proposed) [2.2.2+dfsg-1ubuntu0.2]20:59
stgraberLaney: running with that command still works fine here20:59
stgraberLaney: http://paste.ubuntu.com/23741392/21:01
LaneySomething somewhere is making it break in this specific way :P21:04
LaneyI'll have to look more tomorrow unless one of you gets to it tonight21:04
LaneyFood now21:04
stgraberLaney: what version of LXD are you using on your machine?21:04
stgraberwe did some tweak to exec handling in recent versions (2.6/2.7), wondering if maybe I can't reproduce it because my version isn't affected somehow21:05
barrytsimonq2: ha, yes probably related :)  thanks21:12
Laneystgraber: Right this second I'm on yakkety - seems to be 2.4.121:17
Laneycan't remember offhand what the autopkgtest infrastructure is on, probably x21:17
Laneybet it's something in trusty21:17
stgraberyeah, I'd expect autopkgtest to be on xenial so 2.0.x21:17
stgraberthe exec fixes were in LXD 2.6 or 2.7 so only in zesty so far21:18
stgraberlet me try that against a xenial host21:18
Laneythis means I've seen the same on x, y and z21:18
Laneydoes the spew in the strace log tell you anything?21:19
Laneyprobably should have compressed that21:21
stgrabernot really, sure looks like it's in a loop but there's no sign of it ever getting out of it21:21
stgraberwhich is odd as you should at least see strace exit at some point21:22
* Laney shrugs21:27
LaneyI guess tomorrow, if nobody beats me to it, I'll have to step through everything autopkgtest is doing until it breaks21:28
stgraberno luck with my minimal reproducer on yakkety21:42
barryLaney, stgraber what's going on with autopkgtest?  i don't have any relevant scrollback21:54
infinitybarry: https://bugs.launchpad.net/auto-package-testing/+bug/165402522:01
ubot5`Ubuntu bug 1654025 in Auto Package Testing "trusty/armhf dkms tests are killing workers" [Undecided,New]22:01
infinitybarry: Insights welcome.22:01
barryinfinity: looking22:06
tsimonq2barry: np, it's Really Really Annoying so Please Try And Get It Fixed Pretty Please ;)22:39
barrytsimonq2: oh trust me, i'm hitting it all the time ;)22:40
tsimonq2barry: Relevant systemd bug: https://github.com/systemd/systemd/issues/382622:41
barrytsimonq2: thanks.  i guess i'll subscribe to that ;)22:43
infinityLooks like another case of "systemd thought they knew better", given the implementation is intentionally doing the filtering.22:44
barryplease please please give me systemd-emacs22:44
tsimonq2OH I KNOW! systemd-snapd :P22:45
* tsimonq2 runs22:45
tsimonq2barry: Thanks, slangasek didn't bite when I linked him yesterday, really glad I'm not the only one being tormented ;)22:47
barrytsimonq2: yet another fallout of the pitti defection.  we each inherited 1/10th of a pitti, kind of like a horcrux or something22:48
tsimonq2barry: :P I wish I had the time and expertise to help...22:50
tsimonq2barry: OOH! https://lists.ubuntu.com/archives/ubuntu-devel/2016-December/039564.html22:52
barrytsimonq2: i'm not sure i have either either but i've gotten pretty good at annoyance transfer22:52
barrytsimonq2: yep.  slangasek did suggestion elsewhere a possible revert option until this is fixed22:53
tsimonq2In the worst case, these are the two commits to revert to undo this: https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?id=98974a88 https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?id=47c16e5922:53
tsimonq2barry: imho that would be good, even though my vote probably doesn't count, +3 :P22:55
barrytsimonq2: i think i'll at least test that revert tomorrow22:55
barrythen we can decide after some additional data22:56
tsimonq2barry: And I'd also like to point out that Lubuntu has a bug where ubuntu-standard and ubuntu-minimal (tasks) aren't installed by default, and I Absolutely Hate GUI networking solutions, so there's that...22:57
tsimonq2barry: Heck, I can package the revert now in a PPA of mine and test it quick here :)22:58
tsimonq2As I face it on Real Hardware...22:59
barrytsimonq2: that would be very helpful.  if you do gather useful information, can you please update the LP bug?  i'm very nearly eod and can't run too late tonight.23:02
tsimonq2barry: Sure, although if it's OK with you, I'd like to link the PPA here once I have a solution and at lt have someone else test it ;)23:05
barrytsimonq2: +123:05
tsimonq2barry: OK, cool! I'll let you know! Have a nice night! :)23:05
barrytsimonq2: thanks, you too!23:05
-queuebot:#ubuntu-release- New binary: qbs [ppc64el] (zesty-proposed/universe) [1.7.0+dfsg-3] (no packageset)23:25
-queuebot:#ubuntu-release- New binary: qbs [s390x] (zesty-proposed/universe) [1.7.0+dfsg-3] (no packageset)23:26
-queuebot:#ubuntu-release- New binary: qbs [amd64] (zesty-proposed/universe) [1.7.0+dfsg-3] (no packageset)23:26
-queuebot:#ubuntu-release- New binary: qbs [i386] (zesty-proposed/universe) [1.7.0+dfsg-3] (no packageset)23:28
-queuebot:#ubuntu-release- New binary: qbs [powerpc] (zesty-proposed/universe) [1.7.0+dfsg-3] (no packageset)23:28
-queuebot:#ubuntu-release- New binary: qbs [arm64] (zesty-proposed/universe) [1.7.0+dfsg-3] (no packageset)23:34
-queuebot:#ubuntu-release- New binary: qbs [armhf] (zesty-proposed/universe) [1.7.0+dfsg-3] (no packageset)23:35

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