/srv/irclogs.ubuntu.com/2017/09/19/#ubuntu-release.txt

jbichaI think I'm going to need help with LP: #1718085 tomorrow (or at least this week)02:04
ubot5Launchpad bug 1718085 in ubuntu-gnome-meta (Ubuntu) "FFe: Transition to ubuntu-desktop and provide vanilla-gnome-desktop" [Undecided,New] https://launchpad.net/bugs/171808502:04
jbichaapologies for not doing it sooner, my excuse is that agreeing on a name (even an apparently simple one) is hard02:05
infinityjbicha: Can I bikeshed that name? :P04:06
jbichasure but it might not change the name ;)04:08
UkikieSpeaking of, did anyone look into how notification-daemon slipped into every ISO?04:25
slangasek... no?  which ISO are you expecting it to not be in?04:36
Ukikieslangasek: Xubuntu, Ubuntustudio, Lubuntu and likely Kubuntu, Ubuntu MATE.  The former ship xfce4-notifyd which provides notification-daemon (expected, same as the last many releases) and I presume KDE and MATE provide something as well.04:45
slangasekcyphermox: nplan autopkgtests regressed again?05:20
LocutusOfBorgdoko, I want to see if the llvm fixes are all in debian, I already have a merge ready for the python change (llvm 3.9) http://launchpadlibrarian.net/337517278/llvm-toolchain-3.9_1%3A3.9.1-13ubuntu7_1%3A3.9.1-16.diff.gz I couldn't find references in changelog for the FUZZER change, maybe not needed anymore07:06
* LocutusOfBorg good morning btw07:06
LocutusOfBorgalso ldc should be fixed now07:06
LocutusOfBorgwill appear in some minutes in new queue07:06
-queuebot:#ubuntu-release- New binary: ldc [amd64] (artful-proposed/universe) [1:1.4.0-1ubuntu1] (no packageset)07:16
-queuebot:#ubuntu-release- New binary: ldc [ppc64el] (artful-proposed/universe) [1:1.4.0-1ubuntu1] (no packageset)07:17
-queuebot:#ubuntu-release- New binary: ldc [i386] (artful-proposed/universe) [1:1.4.0-1ubuntu1] (no packageset)07:22
=== Guest19724 is now known as RAOF
LocutusOfBorgdoko, stuff seems to build better with the new ldc https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/debhelper/+build/1339239809:04
LocutusOfBorgwhat is your opinion? it is FTBFS on armhf, but at least if we remove binaries there we can finish the transition09:04
xnoxbdmurray, i believe i have fixed up templates on all the sru bugs =/10:06
dokoLocutusOfBorg: you could do a test build for powerpc on trusty and xenial to see if it is still needed10:21
LocutusOfBorgdoko, context please?10:22
LocutusOfBorgllvm?10:22
dokowell, that's what you asked?10:22
LocutusOfBorgyep, I was wondering about ldc, the second question10:23
LocutusOfBorgactually that FUZZER variable was tested but never defined10:23
dokobetter keep armhf and fix it for th next release10:23
LocutusOfBorgso, in each case, the sync -f has not changed the status quo10:24
LocutusOfBorgfor armhf, I pushed an llvm 5.0 that might fix it10:24
LocutusOfBorg-opt_flags = -g -O210:25
LocutusOfBorg+opt_flags = -g1 -O210:25
LocutusOfBorg+ifneq (,$(filter $(DEB_HOST_ARCH),arm64 ppc64el))10:25
LocutusOfBorg+  opt_flags = -g1 -O210:25
LocutusOfBorg+endif10:25
LocutusOfBorgmaybe you didn't want to change opt_flags regardless of the architecture?10:25
LocutusOfBorgotherwise the if test would have been useless10:25
dokowhy? did you find out what caused the explosion of the debug symbol size?10:27
apwthat is an odd if, it has the same value both ways10:29
apwLocutusOfBorg, ^10:30
LocutusOfBorg^^ that one, the first line10:30
apwas in you reverted the first line10:30
apwof that existing diff ?10:30
LocutusOfBorgAFAIK the explosion of debug symbol size has been a thing in arm64 and ppc64el10:31
LocutusOfBorgso, using -g1 only there should be the exact thing to do10:31
LocutusOfBorgthe above is the diff between the current ubuntu and the current debian10:31
LocutusOfBorg(me, discard the latest sentence)10:32
LocutusOfBorgthe current debian is "good"10:32
* LocutusOfBorg wrt the if statement10:32
LocutusOfBorghttp://launchpadlibrarian.net/337530714/llvm-toolchain-5.0_1%3A5.0-1ubuntu2_1%3A5.0-2~build1.diff.gz10:33
dokono, you are wrong, it' see for s390x as well, even for debian. so please don't speculate10:33
LocutusOfBorglook at the above diff for 5.010:33
LocutusOfBorgit is enabled in +ifneq (,$(filter $(DEB_HOST_ARCH),amd64 arm64 ppc64el s390x))10:34
dokowell, you just said: "the explosion of debug symbol size has been a thing in arm64 and ppc64el"10:36
dokowhich is wrong10:36
LocutusOfBorgyou are right, sorry! I was meaning "for a subset of the whole architecture list", and now debian has that list embedded into the rules file10:37
sergiusensslangasek any update on the armhf network errors?11:26
cyphermoxslangasek: it's possible, but I did run it twice on amd64 before uploading, and both passed no problem. admittedly not against proposed, because proposed was otherwise broken atm (python xml). I'll have a look, given that it passes without proposed, it ought to be a fairly simple debugging session13:32
jbichasil2100: does this look ok? https://code.launchpad.net/~jbicha/ubuntu-cdimage/drop-ubuntu-gnome-artful/+merge/33098313:41
acheronukUkikie: seems notification-daemon is on the Kubuntu iso also. trying to work out how to evict it!14:10
cjwatsonacheronuk: I think it will work if you explicitly seed plasma-workspace in kubuntu.artful/desktop rather than relying on it being pulled in via dependencies.14:15
cjwatsonacheronuk: At the moment, germinate hasn't yet worked out that plasma-workspace is going to be pulled into desktop at the point when it's resolving dependencies (well, Recommends) of libnotify4 while expanding desktop-common, so it picks the real package rather than realising that the Kubuntu-ish replacement is wanted.14:16
acheronukcjwatson: yeah, I'm just weaving my way through those depends and recommends14:17
acheronuklets try that then. see what germinate things on the next iso build14:21
acheronuk*thinks14:21
sil2100jbicha: commented on it14:21
cjwatsonacheronuk: The important bit is explicitly seeding things that you want to be picked instead of the default.14:26
acheronukcjwatson: indeed. thanks for pointing that out. saved me some time puzzling.....14:29
cjwatsonI'm not entirely sure what the problem is in the Xubuntu case.  xfce4-notifyd in core should suffice.14:33
rbasakslangasek: could you accept the python-certbot-nginx binNEW for Xenial please?14:42
cyphermoxslangasek: I re-ran the nplan autopkgtests, currently waiting in the queue. the failure looked like something about the infra though -- as if the tests had been run on the host somehow, and the modules/directories were not cleaned up afterwards -- mac80211_hwsim should never be on any system to begin with, unless it ran the tests and exploded midway :)14:54
ogra_cyphermox, did you see my comment regarding the console-setup udev rule ?14:56
cyphermoxogra_: I did14:56
ogra_good14:56
ogra_someone should at least test if it doesnt break initrd input ... (not sure if it does or does not, but we used to install the rule there)14:56
cyphermoxwell, if it did, it's still being in the way now. I'm sure there is a better way to handle this15:00
cyphermoxthat said, my current thought is why the hell did things need to start using tty1 for graphical, and why can't wayland handle the input correctly anyway?15:00
Laneyit does handle it correctly?15:05
LaneyXorg has the same problem - you can't change the console mode underneath it15:06
slangasekrbasak: done15:07
slangasekcyphermox: ok cool15:07
cyphermoxLaney: things were working fine under X15:07
Laneyno, they worked fine under lightdm/Unity because it was on tty715:07
Laneystart an X session from GDM and reproduce this bug15:07
-queuebot:#ubuntu-release- New: accepted python-certbot-nginx [amd64] (xenial-proposed) [0.14.2-0ubuntu0.16.04.1]15:07
Laneyit happens there too15:07
cyphermoxpartly because things were running on tty7, but I would wager it was also jigling the console modes differently15:07
LaneyNo15:08
LaneyIt's K_OFF, and then when you get K_UNICODE it breaks15:08
cyphermoxI can't begin to explain why you'd see your password in clear text on the screen when it crashes then.15:08
LaneyThat does explain why you see that15:08
cyphermoxand that^ makes me very scared on it15:08
rbasakslangasek: thanks!15:09
Laney...don't switch the keyboard mode...15:09
cyphermoxLaney: not the right place to discuss this in any case.15:09
Laneyk15:09
cyphermoxslangasek: any idea what that issue with nplan might have been?15:10
slangasekcyphermox: nope!15:10
cyphermoxyipee.\15:11
-queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (xenial-proposed) [229-4ubuntu20]15:23
Laneycyphermox: did you try to reproduce this locally?15:24
Laney  File "/tmp/autopkgtest.OH8cTq/build.rJx/nplan-0.28/tests/integration.py", line 104, in create_devices15:24
Laney    raise SystemError('mac80211_hwsim module already loaded')15:24
LaneySystemError: mac80211_hwsim module already loaded15:24
cyphermoxof course I did, it works locally when not using -proposed (because there was another issue with python xml yesterday)15:24
cyphermoxthis is specifically the kind of failure you see if the test previously ran but was killed before the end15:25
cyphermox(ie. cleanup didn't run)15:25
Laneythat paste was from my machine15:25
cyphermoxwhy would this happen though?15:26
cyphermoxdid you use lxc as the runner or qemu?15:26
Laneyqemu15:26
cyphermoxerr15:26
cyphermoxwith proposed?15:27
Laneynplan from proposed15:27
cyphermox--apt-pocket=proposed or not?15:27
Laneyno15:27
Laneyproposed=src:nplan15:27
cyphermoxbecause I had nplan build locally, in that qemu.15:27
cyphermoxie. autopkgtest -U -s . -- qemu ~u/adt-artful-amd64-cloud.img15:28
Laneyautopkgtest.u.c doesn't do it like that15:28
cyphermoxI know that15:28
Laneyok15:29
cyphermoxbut it's the closest I can emulate  "netplan from proposed" without uploading it to proposed.15:29
cyphermoxfurthermore, that has always worked fine until now; so I had no reason to do otherwise.15:30
jbichasil2100: I resubmitted the cdimage change (not sure if it sent you an email or not)15:32
Laneyif you want the actual package from proposed, then --apt-pocket=proposed=src:nplan is the way to ask for that15:32
Laneyyou can see the autopkgtest invocation used near the top of the logs; that helps when reproducing failures15:33
cyphermoxLaney: that's fine once something is in proposed15:34
Laneythis broken nplan is?15:35
cyphermoxmy point was, I tested this locally before uploading, and the autopkgtests were passing with no issues, so I have no idea why it would fail in the infra.15:35
Laneyok, well I came in where there was a claim that the infrastructure was broken and a retry was issued - at that point it was possible to reproduce the same failure without needing local packages15:37
cyphermoxI can't reproduce the failure here.15:37
cyphermoxhttp://paste.ubuntu.com/25573075/15:37
cyphermoxthis is admittedly *not* the same command as you provided, but it *is* the same package being used (it's logged as nplan 0.28)15:37
cyphermoxI'm not claiming that the infra is broken, just trying to figure out where something is different so I know why it works here, but doesn't work in autopkgtests.ubuntu.com15:38
cyphermoxor why it fails for you15:38
cyphermoxugh, that paste is incomplete15:39
cyphermoxthis here is complete: http://paste.ubuntu.com/25573084/15:40
slangaseksergiusens: I've done some quick smoketests and hammering the DNS server from inside with lookups in a loop was not enough to trigger the problem. :/ I'll go ahead and badtest snapcraft/armhf now to let it through, and continue tugging at that problem15:42
slangaseksergiusens: oh, or somebody already did let it through which is also good15:42
slangasek(but didn't badtest it, which is bad)15:43
slangasek(badtest added)15:44
Laneycyphermox: sorry, team meeting --- here's three commands which failed in the same way for me https://paste.ubuntu.com/25573149/, not sure if that's helpful15:51
Laneyit's also a fresh image built 30 minutes ago or so15:52
apwslangasek, how would they have let it through without a badtest/skiptest15:56
cyphermoxLaney: ta. I have an idea, perhaps I know what this is15:56
slangasekapw: because proposed-migration remains completely advisory for SRUs; we need to change sru-release to write hints instead of doing copy-package in order to change this16:12
apwslangasek, derp in a stable release, of course16:12
jbichaslangasek: please update your badtest for (artful) flapak/ppc64el and add s390x (since it's NBS on s390x), also please update the badtest for ostree (L_aney's hint file)17:49
dokoglibc is now only stopped by the libhardware/libhybris stack18:15
slangasekjbicha: fixing the autopkgtest failure is something any Ubuntu dev has access to do; updating the hint is something only the release team can do; why not fixing the flatpak/ppc64el test failure instead?18:23
slangasekand why did flatpak 0.8.7-5 run tests on s390x if there are no binaries :P18:23
sergiusensslangasek thanks, I wasn't even aware it went through! We can certainly look into it live next week and get some proper data to pin point the problem18:26
slangaseksergiusens: yeah... it's confusing, as I said I have seen more lookup failures on armhf than elsewhere, but they've seemed pretty infrequent - not enough for me to expect snapcraft to fail continuously18:27
jbichaflatpak only passed 4 times in its history on ppc64el on Ubuntu so it seems more likely that some change in the infrastructure helped it pass18:30
Ukikieacheronuk: Yeah it looks like a regression somewhere as the package is everywhere, even when an acceptable alternative is seeded.18:47
slangasekinfinity, xnox: were either of you still working the libhybris dep chain?19:58
ahasenackhi, for some reason ubuntu-advantage-tools v8 is in artful/universe instead of main (https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools), could someone "push" it over to main, like it is in all other ubuntu releases before AA?20:10
ahasenackI don't know what happened there, also why it is showing "published 3h ago" when it built back in Aug 22nd20:12
slangasekahasenack: it's in universe instead of main because we haven't yet seeded it in ubuntu-minimal20:14
slangaseksomeone probably demoted it as a component-mismatch20:14
slangasek(which was not wrong; it's on me for not having seeded it before now)20:15
dokoslangasek: please could you skip the autopkg tests for python3-defaults? the queue gets large. I see the the ones for build-essential are almost done, and the ones for python-defaults aretriggerring almost the same packages as python3-defaults20:18
dokoso autopkg tests for universe packages can catch up20:18
xnoxslangasek, why would you want to work on the libhybris dep chain?20:19
slangasekxnox: it's still blocking glibc.  Is there an agreed path forward?  Is someone working on resolving this?20:23
xnoxslangasek, i do not see it blocking glibc20:23
xnoxslangasek, just need to wait for britney to migrate it, as far as i can tell.20:24
xnoxslangasek, publisher is slow20:24
slangasekxnox: did you look at http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt ?20:24
xnoxyes20:24
xnoxslangasek, did you look at https://launchpad.net/ubuntu/+source/libhybris/0.1.0+git20151016+6d424c9-0ubuntu26 ?20:24
slangasekheh20:25
* xnox likes to call & raise20:25
slangasekxnox: you didn't close LP: #1718030 in the changelog :)20:26
ubot5Launchpad bug 1718030 in libhybris (Ubuntu) "libhybris fails to build with glibc 2.26" [Undecided,New] https://launchpad.net/bugs/171803020:26
xnoxslangasek, it's not like it would have made a different until after the package migrates....20:27
dokoslangasek, ahasenack: sorry, yes I demoted it20:27
slangasekxnox: are you sure I'm not scraping changes emails for bug references?20:28
slangasek;)20:28
slangasekxnox: thanks for the fix20:28
xnoxslangasek, if you were scrapping changes emails, you would have noticed that i uploaded libhybris ;-)20:28
slangasekxnox: not if I was filtering for bugs I care about!20:29
slangasekit's plausible20:29
xnoxdeniability20:30
xnoxanyway. publisher is so slow20:30
slangasekpublisher, or britney?20:30
slangasekpublisher says it's published.  britney doesn't show it moving20:31
xnoxit's not yet even in rmadison output20:31
slangasekrmadison is post-publisher20:31
-queuebot:#ubuntu-release- Unapproved: cockpit (zesty-backports/universe) [148-1~ubuntu17.04.1 => 150-2git1~ubuntu17.04.1] (no packageset)20:31
xnox... and the builds finished building 1h ago, hence i blame publisher for the delays20:32
slangasekdoko: I only see long 'huge' queues of autopkgtests, not regular queues.  It's fine for these autopkgtests to run as low-priority jobs, unless there are things queued behind these in the 'huge' queue that you care about?20:32
xnoxbritney doesn't notice things until they are in rmadison. Maybe imprecise timing, but that is my perception from how things look to me.20:32
-queuebot:#ubuntu-release- Unapproved: cockpit (xenial-backports/universe) [148-1~ubuntu16.04.1 => 150-2git1~ubuntu16.04.1] (no packageset)20:32
slangasekdoko: also, dumping the tests is different than letting python3-defaults through before the tests are done; is the latter what you care about?20:33
xnoxdoko, do you need that package to start archive rebuild or something?20:33
dokoslangasek: sure, fine. please lower the priority and enjoy yourself looking at the logs ;p20:33
slangasekxnox: britney talks to ftpmaster.internal directly.  rmadison data is generated from ftpmaster.internal.20:33
dokoxnox: I've given up on that. will do the tst rebuild with -proposed enabled :/20:34
slangasekdoko: they are already in the low-priority queue20:34
xnoxdoko, or is that the fix for parsing that debian file?20:34
-queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (xenial-backports) [150-2git1~ubuntu16.04.1]20:34
-queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (zesty-backports) [150-2git1~ubuntu17.04.1]20:34
dokoxnox: no, it's just a version bump20:34
xnoxdoko, yeah anything that triggers more than a few tests automatically ends up in a different queue in the autopkgtests.20:34
xnoxit's round robin across ubuntu, ppas, upstream, and "things that triggered a lot of tests". To not starve "small" upgrades, by the "large ones".20:35
xnoxbut i think it does not do round-robin across releases20:35
slangasekI think it is20:35
xnoxthus one has to wait for xenial to be drained before artful is tested.20:35
xnoxhm, ok.20:35
slangasekdoko: I'm not opposed to doing something here to expedite.  what I'm asking is that we be clear about what we're doing, and the rationale.  Clearing the autopkgtest queues doesn't make python3-defaults migrate any faster; adding a skiptest hint for python3-defaults would make it migrate faster20:37
dokoslangasek: well, it's not that these autopkg tests would catch anything which is not already in the release pocket20:38
slangasekdoko: ok, but what is it that you are trying to accomplish? "empty autopkgtest queues" is not a goal that gets me out of bed20:39
slangasekis something that you care about blocked / slow?20:39
xnoxslangasek, hm so new publisher run does not start until after a britney run finishes? i would have thought that is decoupled.20:39
xnoxslangasek, such that things in -proposed can publish multiple times whilst britney is running20:39
dokolol, 1pm in bed?20:40
xnoxshhh20:40
slangasekxnox: they are decoupled.  I was only saying that if you want to know when britney will see it, looking in rmadison has false-negatives20:40
slangasekdoko: a saying20:40
dokoslangasek: britney runs are currently slow, for whatever reason20:40
slangasekyes.  maybe they're slow because they're trying to check a lot of autopkgtest results20:41
xnoxslangasek, so a run 20 minutes ago, did not notice libhybris that finished 1h ago and published 57 minutes ago?20:42
xnoxalthough it may be a lie that it published 57 minutes ago, could have been just the source publication20:42
slangasekxnox: the 'generated' timestamp is near the end of the britney run, not the start, fwiw20:42
xnoxlooking at the current running log at http://people.canonical.com/~ubuntu-archive/proposed-migration/log/artful/2017-09-19/20:20:05.log20:43
xnoxbritney run that "started" 20 minutes ago20:43
slangasekxnox: right, new update_excuses up and still no libhybris; I'll dig if time allows, but I have a call in 10 minutes20:49
xnoxslangasek, and now that that britney is done, new libhybris appeared in rmadison, and i suspect next run of britney will have the new libhybris.20:51
xnoxit does feel like britney locks and block ftpmaster.internal20:51
slangasekit doesn't20:52
xnoxmigrating \o/21:13
dokowonders still happen21:18
slangasekuh21:20
slangasekarpack++ now shows up as a regression under glibc, where did that come from?21:20
slangasekskiptested, so not fatal, but21:20
slangasekoh, because it passed for the first time with new openblas, so it's a retroactive regression ;P21:21
dokonow finally clang demoted to universe. we really should take more care about auto promotions to main21:57
infinityxnox: \o/22:17
tsimonq2Release team: I'd like to do a change to gdebi that's all in one upload. One change (that I've already made locally) fixes a bug that Ubuntu MATE was having, the other thing that I would like to do is port away from the obsolete, insecure framework kdesudo and instead use kdesu for gdebi-kde. kdesudo has already been removed in Debian because it's KDE 3 and hasn't been touched upstream since23:11
tsimonq22011. Can I JFDI or do you want me to file a bug for the FFe for the kdesudo port?23:11
tsimonq2I just don't know if it deserves an FFe.23:11
tsimonq2I'd consider it a bugfix in the sense that kdesu is generally more secure and has less bugs, but a feature in the sense that it's porting to a new framework.23:12
tsimonq2Thoughts?23:12
naccif someone from the release team could review the FFE at LP: #1658469, I'd appreciate it.23:18
ubot5Launchpad bug 1658469 in apache2 (Ubuntu) "[FFe] mod_http2 is not available in Apache" [Low,Triaged] https://launchpad.net/bugs/165846923:18
tsimonq2(actually, might work better as separate gdebi upload, let's get that out of the way)23:28
tsimonq2(bugfix)23:28
-queuebot:#ubuntu-release- New binary: cockpit [amd64] (xenial-backports/universe) [150-2git1~ubuntu16.04.1] (no packageset)23:46

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