/srv/irclogs.ubuntu.com/2016/10/11/#ubuntu-release.txt

-queuebot:#ubuntu-release- Unapproved: gnome-devel-docs (yakkety-proposed/universe) [3.22.0-1 => 3.22.1-0ubuntu1] (desktop-extra)00:00
tsimonq2sarnold: around? I'd like to get bug 1630700 fast-tracked through00:02
ubot5bug 1630700 in kcoreaddons (Ubuntu Precise) "CVE - KMail - HTML injection in plain text viewer" [Undecided,In progress] https://launchpad.net/bugs/163070000:02
-queuebot:#ubuntu-release- Unapproved: ansible (xenial-proposed/universe) [2.0.0.2-2 => 2.0.0.2-2ubuntu1] (no packageset)00:03
infinitywgrant: If a custom kernel will get us over the hump Right Now, let's do it.01:15
infinitywgrant: Agreed it's a terrible long-term solution, but not being able to build things we want on images today is also pretty ungood.01:15
wgrantinfinity: Absolutely.01:17
infinitywgrant: Other than kernel build time, which I'm intimately familiar with, what kind of turnaround could we get on that?01:17
wgrantinfinity: Soon™01:18
infinity(And said kernel could be neutered in debian/rules to exit 1 on DPKG_BUILD_ARCH != arm64, arm64 actually builds pretty fast compared to most)01:18
infinityErr, HOST_ARCH.01:18
infinityThough either would work in a non-cross env. :P01:18
wgrantinfinity: We can get new images out in less than half an hour one the packages are available.01:20
wgrantUsually well less than half an hour, now that arm64 VMs aren't silly :)01:20
-queuebot:#ubuntu-release- Unapproved: linux-meta-snapdragon (xenial-security/universe) [4.4.0.1030.22 => 4.4.0.1030.22] (kernel) (sync)01:21
-queuebot:#ubuntu-release- Unapproved: accepted linux-meta-snapdragon [sync] (xenial-security) [4.4.0.1030.22]01:22
infinitywgrant: Need any help wrangling kernel packaging, or are you good there?01:23
wgrantinfinity: I'm reasonably competent, particularly when not changing ABI :)01:23
-queuebot:#ubuntu-release- Unapproved: rejected linux-meta-snapdragon [sync] (xenial-security) [4.4.0.1030.22]01:23
infinitywgrant: Heh.  When not changing ABI, the best trick is to append to the current changelog entry and NOT MAKE A NEW ONE.01:23
infinityThen no ABI checker invoked, and magic.01:23
wgrantPrecisely.01:24
infinitywgrant: Right, then I'll keep out of your hair.01:24
wgrantIt took me a couple of years to work that hack out.01:24
infinitywgrant: Lemme know when you think it's ready for a spin, and I'll lob things at it.01:24
infinityI should be up for a Very Long While still.01:25
infinityIn the process of reversing my clock.01:25
infinityWell, inverting, not reversing.01:25
wgrantinfinity: It'll be a good while, currently in a couple of meetings.01:25
wgrantThough hopefully wrapping up now, then will get onto it properly.01:25
infinitywgrant: All good.  I intend to be awake all through London work day.01:25
infinitywgrant: TO set a trend for the rest of the week.01:25
infinityHow I plan to do this, given that I woke up at 7am Calgary time, I'm not yet sure.01:26
infinityBut I suspect caffeine might come into play.01:26
-queuebot:#ubuntu-release- Unapproved: debian-installer (yakkety-proposed/main) [20101020ubuntu481 => 20101020ubuntu482] (core)01:29
tsimonq2infinity: Staying on UK time zones are fun, I did that over my summer vacation for a few weeks. :P01:30
infinitytsimonq2: I do it all the time, but it's always harder to shift one's clock on purpose rather than by accident. :P01:30
tsimonq2infinity: I can agree with that.01:31
-queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (yakkety-proposed) [20101020ubuntu482]01:31
-queuebot:#ubuntu-release- Unapproved: accepted thunderbird [source] (yakkety-proposed) [1:45.3.0+build1-0ubuntu2]01:31
-queuebot:#ubuntu-release- Unapproved: accepted gnome-devel-docs [source] (yakkety-proposed) [3.22.1-0ubuntu1]01:32
-queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-340 [source] (yakkety-proposed) [340.98-0ubuntu1]01:34
cyphermoxinfinity: logging off for some sleep. use ancient communication methods should you really need me for some reason.01:46
-queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Yakkety Final] has been updated (20161011)01:47
-queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Yakkety Final] has been updated (20161011)01:47
-queuebot:#ubuntu-release- Builds: Netboot amd64 [Yakkety Final] (20101020ubuntu482) has been added02:30
-queuebot:#ubuntu-release- Builds: Netboot arm64 [Yakkety Final] (20101020ubuntu482) has been added02:30
-queuebot:#ubuntu-release- Builds: Netboot armhf [Yakkety Final] (20101020ubuntu482) has been added02:30
-queuebot:#ubuntu-release- Builds: Netboot i386 [Yakkety Final] (20101020ubuntu482) has been added02:30
-queuebot:#ubuntu-release- Builds: Netboot powerpc [Yakkety Final] (20101020ubuntu482) has been added02:31
-queuebot:#ubuntu-release- Builds: Netboot ppc64el [Yakkety Final] (20101020ubuntu482) has been added02:31
-queuebot:#ubuntu-release- Builds: Netboot s390x [Yakkety Final] (20101020ubuntu482) has been added02:31
apwcjwatson, normally in 64bit all of physical memory is "direct mapped" so if the h/w is using a large physical space then we will chew a large chunk of KVA for the direct map03:47
apwstill not clear as to why that is visible in userspace in any sense03:50
=== maclin1 is now known as maclin
-queuebot:#ubuntu-release- New sync: openfoam (yakkety-proposed/primary) [4.0+dfsg1-3]06:01
-queuebot:#ubuntu-release- Unapproved: python3.6 (yakkety-proposed/universe) [3.6.0~b1-1ubuntu2 => 3.6.0~b2-1] (no packageset)06:12
-queuebot:#ubuntu-release- Unapproved: accepted python3.6 [source] (yakkety-proposed) [3.6.0~b2-1]06:13
-queuebot:#ubuntu-release- New: accepted linbox [arm64] (yakkety-proposed) [1.4.2-1~build1]06:18
-queuebot:#ubuntu-release- New: accepted linbox [i386] (yakkety-proposed) [1.4.2-1~build1]06:18
-queuebot:#ubuntu-release- New: accepted linbox [armhf] (yakkety-proposed) [1.4.2-1~build1]06:19
-queuebot:#ubuntu-release- New: accepted linbox [ppc64el] (yakkety-proposed) [1.4.2-1~build1]06:19
-queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-304 (yakkety-proposed/restricted) [304.131-0ubuntu5 => 304.132-0ubuntu1] (ubuntu-desktop)08:19
=== jamespag` is now known as jamespage
=== santa is now known as Guest77141
=== michihenning is now known as michi
pittiinfinity, apw: I'm going to kill the currently running linux tests again, as they still keep breaking the testbed and are stuck in an eternal retry loop;  but I'll try to collect the console-log this time09:15
=== marcusto_ is now known as marcustomlinson
pittiapw: filed bug 1632252 with some logs/details09:27
ubot5bug 1632252 in linux (Ubuntu) "linux autopkgtest kills sshd in testbed" [Undecided,Confirmed] https://launchpad.net/bugs/163225209:27
pittiapw: sounds like sshd gets OOM-killed09:27
-queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Yakkety Final] has been updated (20161011)09:52
-queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Yakkety Final] has been updated (20161011)09:52
-queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop powerpc [Yakkety Final] has been updated (20161011)09:52
-queuebot:#ubuntu-release- Unapproved: update-manager (yakkety-proposed/main) [1:16.10.6 => 1:16.10.7] (core)09:55
pittiinfinity, slangasek: ^ this drops the hard python3-launchpadlib dependency again (from http://launchpadlibrarian.net/275354292/update-manager_1%3A16.10.2_1%3A16.10.3.diff.gz) and adds a graceful fallback09:56
pittithis should clean up most of http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt09:56
cjwatsonwhich will mean that the PPA changelog handling randomly doesn't work for users depending on whether they happen to have python3-launchpadlib installed?10:03
cjwatsonI mean, I guess I see why you're doing it, but avoiding this was why I asked in review of that feature for it to be just made a dependency rather than conditional10:04
pitticjwatson: I'd rather seed python3-launchpadlib on desktop then, TBH10:04
pitti maybe the feature can also be reworked to do a single REST call via urllib, but I don't want to do this "under the gun"10:05
cjwatsonpitti: seeding in desktop seems like a reasonable compromise, if people are OK with that10:05
pittiit doesn't do anything authenticated, so I guess getting a changelog with plain urllib should be fairly easy10:05
cjwatsonmaybe as a Recommends10:05
pitti*nod*10:05
pittinot sure who has the last word on that, but I'm happy to make the seed changes and update ubuntu-meta if we want to go ahead with this10:06
cjwatsonIt should be relatively easy to redo by-hand without lplib, indeed10:06
cjwatsonOne problem with seeding in desktop is, which desktops10:06
pittihm -- how about we move the Depends: to update-manager?10:08
pitti(it previously was on python3-update-manager which is in standard)10:08
pittiupdate-manager is optional10:08
pittithen we don't need seed changes, and this conceptually sounds "more correct"10:09
pittiand to u-m-kde10:09
* pitti self-rejects and reuploads, that's better than fiddling with seeds10:10
cjwatsonSeems reasonable if you retain the optionality in the code10:10
cjwatsonThis is how to do what u-m does by hand:10:11
cjwatson$ curl -s 'https://api.launchpad.net/devel/archives?ws.op=getByReference&reference=%7Ecjwatson/ubuntu/ppa' | jq .self_link10:11
cjwatson"https://api.launchpad.net/devel/~cjwatson/+archive/ubuntu/ppa"10:11
cjwatson$ curl -s 'https://api.launchpad.net/devel/~cjwatson/+archive/ubuntu/ppa?ws.op=getPublishedSources&source_name=ant&exact_match=true&version=1.9.7-3ppa1' | jq '.entries[0].self_link'10:11
-queuebot:#ubuntu-release- Unapproved: rejected update-manager [source] (yakkety-proposed) [1:16.10.7]10:11
cjwatson"https://api.launchpad.net/devel/~cjwatson/+archive/ubuntu/ppa/+sourcepub/6712285"10:11
cjwatson$ curl -s 'https://api.launchpad.net/devel/~cjwatson/+archive/ubuntu/ppa/+sourcepub/6712285?ws.op=changelogUrl' | jq10:11
cjwatson"https://launchpad.net/~cjwatson/+archive/ubuntu/ppa/+sourcepub/6712285/+files/changelog"10:11
cjwatsonbut you do have to make sure that all the quoting is correct10:11
pittiyeah, TBH that sounds more like a z thing10:12
cjwatsonhttps://api.launchpad.net/devel/archives is a hardcoded base, and all of reference, source_name, and version are inputs that must be URL-escaped10:12
cjwatsonEasy enough, but yeah, can be done in z10:13
cjwatson(Do we have a name yet?)10:14
pittifor the Zealous Zombie?10:15
Odd_BlokeZenial Zebra.10:16
-queuebot:#ubuntu-release- Unapproved: update-manager (yakkety-proposed/main) [1:16.10.6 => 1:16.10.7] (core)10:16
acheronuksome have been guessing at Zazzy Zorilla10:17
pittiinfinity, slangasek: ^ updated update-manager as per discussion with cjwatson; this is now self-contained (does not need seed changes)10:17
pittiI think we can drop xml-core's Depends: perl, to clean up that from "standard" as well (only using modules from perl-base); will confirm and then upload/file Debian bug10:18
pittiwith these two, the remaining priority-mismatch items should be valid10:19
cjwatsonacheronuk: Yeah, I'm ignoring guesses because they're ~never right10:20
cjwatsonpitti: the changelog seems a bit wrong now?10:21
cjwatsonpitti: wait, maybe I'm suffering from caching10:21
pitticjwatson: ah, it should probably say "lower .. from python3-update-manager's Depends"?10:21
pitticjwatson: http://launchpadlibrarian.net/289188605/update-manager_16.10.7_source.changes is the current version that I uploaded10:22
cjwatsonno, I'm OK with it once I avoid looking at the old cached version10:22
cjwatson(but am no longer release team, so not accepting)10:22
acheronukcjwatson: yep, my guess always seems wrong10:24
-queuebot:#ubuntu-release- Unapproved: xml-core (yakkety-proposed/main) [0.15 => 0.15ubuntu1] (core)10:54
pitti^ will fix the perl priority-mismatches. This was a recent regression from https://anonscm.debian.org/git/debian-xml-sgml/xml-core.git/commit/?id=fed34e010:55
pittii. e. accidentally dropping the dh_perl -d option10:56
pitti(also filed as Debian bug 840410)10:56
ubot5Debian bug 840410 in xml-core "xml-core: Drop perl dependency" [Wishlist,Open] http://bugs.debian.org/84041010:56
pittiLaney: ^ as this is quite straightforward, mind reviewing/accepting this?10:56
pittireviewing u-m is also appreciated of course, to clean up most of priority-mismatches so that we can get it release-ready10:57
Laneypitti: sure11:06
tsimonq2cjwatson: I'm still voting for Zealous Zebu :P11:13
tsimonq2s/voting/hoping/11:13
acheronuktsimonq2: lol. you changed your mind AGAIN?11:16
tsimonq2acheronuk: no I only said Zazzy Zorilla because I thought Barry Warsaw leaked the codename, turns out he made it up... :P11:17
acheronuktsimonq2: I swear there is a subtle disinformation plot by canonical each year to keep the real one under wraps11:18
-queuebot:#ubuntu-release- Unapproved: accepted xml-core [source] (yakkety-proposed) [0.15ubuntu1]11:19
tsimonq2acheronuk: cjwatson linked me to a graph yesterday...11:19
* tsimonq2 finds it11:20
tsimonq2acheronuk: http://people.canonical.com/~cjwatson/tmp/release-name-notice.png11:20
acheronukinteresting11:22
Laneypitti: unorthodox syntax on Suggests there11:32
* Laney built it to check it works (it does)11:32
* rbasak believes he predicted Yakkety Yak before it was named11:33
rbasakThough in hindsight it was obvious I guess11:33
Laneyand argh at all the trailing spaces in update-manager/d/control11:33
Laney(not new)11:34
=== Guest77141 is now known as santa_
-queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (yakkety-proposed) [1:16.10.7]11:35
-queuebot:#ubuntu-release- Unapproved: budgie-desktop (yakkety-proposed/universe) [10.2.7-2 => 10.2.7-3] (no packageset) (sync)11:44
-queuebot:#ubuntu-release- Unapproved: accepted budgie-desktop [sync] (yakkety-proposed) [10.2.7-3]11:44
pittiLaney: you mean trailling commas?11:46
pittiLaney: trailing spaces> yeah, my vim loudly complains too, but minimal diff for review, etc.11:47
Laneypitti: It's like11:49
LaneySuggests:11:49
Laney          python3-...11:49
-queuebot:#ubuntu-release- Unapproved: congress (yakkety-proposed/universe) [4.0.0~rc1+dfsg1-1 => 4.0.0+dfsg1-2] (no packageset) (sync)11:57
-queuebot:#ubuntu-release- Unapproved: accepted congress [sync] (yakkety-proposed) [4.0.0+dfsg1-2]11:57
-queuebot:#ubuntu-release- Unapproved: juju-core (yakkety-proposed/main) [2.0~rc3-0ubuntu2.16.10.1 => 2.0~rc3-0ubuntu3.16.10.1] (ubuntu-server)12:31
cyphermoxgood morning12:32
pittiLaney: oh, oops12:33
pittiLaney: fixed in bzr12:33
pittihey cyphermox12:33
-queuebot:#ubuntu-release- Unapproved: designate-dashboard (yakkety-proposed/universe) [3.0.0~rc1-1 => 3.0.0-2] (no packageset) (sync)12:34
-queuebot:#ubuntu-release- Unapproved: accepted designate-dashboard [sync] (yakkety-proposed) [3.0.0-2]12:35
-queuebot:#ubuntu-release- Unapproved: accepted juju-core [source] (yakkety-proposed) [2.0~rc3-0ubuntu3.16.10.1]12:36
pittiapw: do you know about the fate of http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#linux ?12:37
pittiI suppose we should release that RSN so that we can rebuild images?12:37
apwpitti as far as i can tell it is as good as the previous one, so i guess as those tests are not going to ever come in we'll need to hint it12:41
pittiapw: oh right -- I was blindly assuming they would use a tracking bug12:43
pittiapw: hinting12:43
pittiseb128, jbicha: do we want to let bug 1631955 into yakkety, or remain as an SRU?12:45
ubot5bug 1631955 in evolution-data-server (Ubuntu Yakkety) "Update e-d-s to 3.22.1" [Medium,Fix committed] https://launchpad.net/bugs/163195512:45
pitti(seb128, jbicha: we still have a kernel and two other packages to land before respinning images)12:46
seb128pitti, letting jbicha comment, I didn't look at this update12:46
seb128pitti, we don't plan respins after that?12:46
pittiseb128: I don't know; just saying that the current images can't possibly be final12:47
seb128pitti, it's a bit suboptimal that we have the current firefox blocked in proposed but I guess it is what it is now?12:47
seb128k12:47
pittiseb128: well, firefox is FTBFS, not much that we can do other than fixing it12:47
pittibut that's fine as an SRU12:48
seb128not optimal though12:48
seb128there might be some security issues in the previous verison12:49
seb128oh, also that's using an google api key that we revocated12:49
seb128the new key was added in https://launchpad.net/ubuntu/+source/firefox/49.0+build4-0ubuntu112:49
pittiwell, if we have a fix now/today, I'm sure everyone would be happy to get it in :)12:49
seb128chrisccoulson, ^12:49
seb128pitti, or we could declared firefox unsupported on ppc64el like it is on powerpc and s390x and delete the binaries like we did for those...12:50
chrisccoulsonI don't think I'll be able to spend time investigating a ppc64el-specific startup crash in Firefox tbh12:51
jbichapitti: I'm ok with letting e-d-s in now, it worked fine for me12:51
chrisccoulson(which is what the build failure is)12:51
jbichathe new e-d-s apparently doesn't actually fix the google authentication problem12:51
jbichaI guess we can point ppc users to epiphany? since chromium isn't supported there either12:54
-queuebot:#ubuntu-release- Unapproved: python-pycadf (yakkety-proposed/main) [2.2.0-2 => 2.4.0-1] (ubuntu-server) (sync)12:58
chrisccoulsonseb128, have you used firefox in proposed btw?13:11
seb128chrisccoulson, not really, but I can give it a try if you want ... anything in particular?13:11
seb128chrisccoulson, did you see the ping from rico early on ubuntu-devel btw?13:11
chrisccoulsonseb128, well, I just thought - the build in the release pocket is now so ancient that it was built with the old compiler13:12
chrisccoulsonI didn't see a ping earlier, let me check13:12
seb128chrisccoulson, it was at 8:25 u.k13:13
chrisccoulsonahh13:13
chrisccoulsonso, firefox has the same issue as https://bugs.chromium.org/p/v8/issues/detail?id=3782 which already affected chromium and oxide13:13
chrisccoulsonFirefox really needs a maintainer that cares about it ;)13:14
chrisccoulsonoh, apparently firefox doesn't have this problem, and the bug ricotz linked is thunderbird specific13:17
=== barry` is now known as barry
jbichachrisccoulson: I've been using firefox from y/proposed for several days and it seems ok13:22
apwand the one from release is dire :/13:35
-queuebot:#ubuntu-release- Unapproved: llvm-toolchain-3.5 (yakkety-proposed/universe) [1:3.5.2-3ubuntu1 => 1:3.5.2-5] (no packageset) (sync)13:42
-queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-3.5 [sync] (yakkety-proposed) [1:3.5.2-5]13:43
=== medberry is now known as med_
=== jgrimm-out is now known as jgrimm
balloonspitti, nothing is running in autopkgtest?14:02
-queuebot:#ubuntu-release- Unapproved: xfsprogs (yakkety-proposed/main) [4.3.0+nmu1ubuntu2 => 4.3.0+nmu1ubuntu3] (core)14:07
apw^ fixes fallout from v4.8 kernel headers ...14:07
davmor2cyphermox: how are we looking for the new shim do you know anything yet?14:14
-queuebot:#ubuntu-release- Unapproved: openorienteering-mapper (yakkety-proposed/universe) [0.6.3-2build1 => 0.6.5-1] (no packageset) (sync)14:30
-queuebot:#ubuntu-release- Unapproved: accepted openorienteering-mapper [sync] (yakkety-proposed) [0.6.5-1]14:31
pittiballoons: no, we are in freeze :)14:36
pittiballoons: juju is, actually (i386 and amd64 failed already)14:37
-queuebot:#ubuntu-release- Unapproved: gdb (yakkety-proposed/main) [7.11.90.20161005-0ubuntu1 => 7.12-0ubuntu1] (core)14:37
balloonspitti, right it was of course what I was looking for. I saw amd64 failed, but I can't see the log proper until it finishes -- unless there's something I don't know14:37
-queuebot:#ubuntu-release- New: accepted openfoam [sync] (yakkety-proposed) [4.0+dfsg1-3]14:38
cyphermoxdavmor2: sorry, no news to be given14:39
pittiapw: xfsprogs> cheers! is that an upstream backport?14:40
-queuebot:#ubuntu-release- Unapproved: accepted xfsprogs [source] (yakkety-proposed) [4.3.0+nmu1ubuntu3]14:41
apwpitti, no that is allll me14:41
-queuebot:#ubuntu-release- Unapproved: accepted gdb [source] (yakkety-proposed) [7.12-0ubuntu1]15:04
-queuebot:#ubuntu-release- Unapproved: vlan (xenial-proposed/main) [1.9-3.2ubuntu1 => 1.9-3.2ubuntu1.16.04.1] (core)15:04
-queuebot:#ubuntu-release- Unapproved: vlan (precise-proposed/main) [1.9-3ubuntu6 => 1.9-3ubuntu6.1] (kubuntu, netbook, ubuntu-desktop, ubuntu-server, unr)15:05
-queuebot:#ubuntu-release- Unapproved: vlan (trusty-proposed/main) [1.9-3ubuntu10 => 1.9-3ubuntu10.1] (core)15:05
-queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (yakkety-proposed/partner) [1:20160913.1-0ubuntu1 => 1:20161011.1-0ubuntu1] (no packageset)15:16
pittichrisccoulson, seb128: removing current ppc64el firefox binaries seems reasonable to me; Laney, infinity, opinions?15:21
chrisccoulsonpitti, I should point out, we don't block firefox security updates for build failures on those 3 architectures anyway15:22
chrisccoulsonAnd the updates are never tested on those architectures in any case15:22
seb128pitti, +1 from me, it might require to delete/tweak a bit more due to rdepends, whoever handled the drop of powerpc earlier in the cycle should know the details of what is needed though15:23
pitti firefox | 49.0+build4-0ubuntu0.16.04.1   | xenial-security  | source, amd64, arm64, armhf, i386, ppc64el15:23
pitti chrisccoulson: I was wondering because it apparently did build for xenial still -- gcc 6, presumably?15:24
chrisccoulsonpitti, I uploaded thunderbird with a build failure fix, but I've since been made aware of https://bugzilla.mozilla.org/show_bug.cgi?id=1251576, so it won't run anyway (it's a similar issue to https://bugs.chromium.org/p/v8/issues/detail?id=3782, which we already worked around in chromium and oxide)15:24
ubot5Mozilla bug 1251576 in General "GCC6 - TB crashes due to removed null pointer checks for "this"" [Normal,New]15:24
chrisccoulsonpitti, yeah, most likely15:24
-queuebot:#ubuntu-release- Unapproved: libreoffice (yakkety-proposed/main) [1:5.2.2-0ubuntu1 => 1:5.2.2-0ubuntu2] (kubuntu, ubuntu-desktop)15:25
Laneypitti: We forced it last time15:25
pittiLaney: you mean with a britney hint, not removing packages?15:26
Laneyyep15:26
pittithat seems a bit awkward15:26
Laneywhy?15:26
pittiLaney: hm, does that still turn up at NBS?15:26
pittiour report doesn't show that, AFAIK it only runs for amd6415:27
jbichaFirefox shows up at the bottom of /update_output.txt15:28
pittiList of old libraries in testing (2):15:28
pitti  firefox: s390x powerpc15:28
pittioh, this?15:28
pittiwell, we really should remove the old binaries properly15:28
* pitti → meeting, bbl15:29
-queuebot:#ubuntu-release- Unapproved: unattended-upgrades (yakkety-proposed/main) [0.92 => 0.92ubuntu1] (desktop-core, ubuntu-server)15:49
-queuebot:#ubuntu-release- Unapproved: python-tornado (yakkety-proposed/universe) [4.4.1-2ubuntu1 => 4.4.2-1ubuntu1] (ubuntu-desktop)16:00
slangasekpitti, balloons, stokachu: seems that juju-core is still failing autopkgtests, has this been analyzed?16:01
pittislangasek: yes, balloons and I just debugged it16:01
pittislangasek: ballons is preparing a new .dsc, I'll sponsor16:01
balloonsslangasek, yes it's sorted. ^^16:01
-queuebot:#ubuntu-release- Unapproved: accepted python-pycadf [sync] (yakkety-proposed) [2.4.0-1]16:01
pittibuilding from bzr doesn't work (source and pristine-tar disagree), so I'll let him sort out the source build16:01
balloonsand sorry pitti, re-setting up vpn to upload dsc16:01
pittiballoons: that or pastebin a debdiff if that's easier16:02
lunaphytehi.  i'm trying to upgrade an eol install [15.04] to 15.10 [this is all just to upgrade to 16.04].  but if i'm not mistaken, the old-releases repo doesn't have packages/indexes for 15.10 published, so i'm stuck, it seems.16:18
lunaphytehowever, us.archive.ubuntu.com still does.  so i'm a little confused as to how to go about upgrading.16:18
wxllunaphyte: #ubuntu for support.16:18
lunaphyte[and, if this is the wrong channel, apologies]16:19
lunaphytewxl: i actually came here from #ubuntu-server16:19
wxllunaphyte: they suggested to come here? because that's strange. this channel exists to coordinate upcoming releases.16:20
lunaphyteit seems though that vivid package indexes aren't listed at old-releases, yet they should be, hence my question here16:20
lunaphytewxl: no, they didn't suggest.  i spent time there troubleshooting, that's all.16:20
wxllunaphyte: i'd personally advice you grab /home and maybe /etc and do a fresh install re-using those16:20
lunaphytehonestly, i'd just like to know who i can ask about 15.04 missing from old-releases16:21
wxllunaphyte: vivid and wily are both at archive.ubuntu.com16:24
-queuebot:#ubuntu-release- Unapproved: accepted maas [source] (yakkety-proposed) [2.1.0~beta2+bzr5454-0ubuntu1]16:25
-queuebot:#ubuntu-release- Unapproved: networking-hyperv (yakkety-proposed/universe) [2.0.0-0ubuntu1 => 3.0.0-0ubuntu1] (no packageset)16:26
lunaphytei thought since vivid is eol, it would be at old-releases.16:26
wxlit will get there eventually, i'm sure16:26
-queuebot:#ubuntu-release- Unapproved: accepted networking-hyperv [source] (yakkety-proposed) [3.0.0-0ubuntu1]16:26
lunaphyteinex retrieval at archive.ubuntu.com does work for vivid, yes, but upgrading fails, because it tries to upgrade to 16.04, but do-release-upgrade doesn't support it, of course.16:27
wxlso like i said, fresh install16:27
lunaphytewxl: thanks, yeah, i guess that's my question, is what typically defines when that happens?16:27
chrisccoulsonpitti, are you able to approve partner uploads?16:28
lunaphytewxl: it's ok, i'll let the channel get back to the /topic16:28
wxlinfinity: could you answer lunaphyte's question as to why vivid and wily are not in old-releases but are instead still on archive?16:28
lunaphytehopefully my question isn't interpreted as "when will this be" - just would like to understand what the transition is based on16:29
wxlmany activities in release require manual activity (for example, turning dailies on and off in response to milestone testing)16:30
cjwatsonlunaphyte: Can't give you an accurate answer as to why it's not done yet (I suspect not-got-round-to-it for wily, and complicated stuff involving the Ubuntu phone codebase for vivid), but the process doc is https://wiki.ubuntu.com/EndOfLifeProcess16:30
wxlthat said, sometimes they just get temporarily forgotten or put off16:30
rbasakThere is no definite schedule. The EOL date is one bound.16:31
wxltl;dr lesson learned: upgrade BEFORE EoL :)16:31
lunaphytecjwatson: ah, thanks, that's informative16:31
lunaphytewxl: yeah, for sure.  life sometimes has other plans, unfortunately. :)16:31
lunaphyteit's all good though.16:31
apwwell before EOL of the release which follows :)16:32
cjwatsonI'd probably just upgrade by frobbing sources.list and doing a dist-upgrade.16:32
wxlapw: hahahah indeed16:32
cjwatsonSure, do-release-upgrade helps, but it isn't mandatory.16:32
lunaphyteif the end result is that eventually it will make it's way to old-releases, and then the nominal eol upgrade path will work as expected, that's fine16:32
rbasakSomebody should figure out and document how to handle this better on the existing wiki page.16:32
pittichrisccoulson: technically, yes; procedurally I have no idea what to do with them/what to check, etc.16:33
lunaphytecjwatson: does frobbing sources.list mean switching from vivid to wily, in my case?16:33
rbasakhttps://help.ubuntu.com/community/EOLUpgrades16:33
lunaphytei'm but a visitor here, but would a note somewhere there along the lines of "if you are doing an eol upgrade of a relatively recent release, it's possible that it may not work, until various transitions have fully occured - please try again later" be of any value?16:36
chrisccoulsonpitti, ah. I need adobe-flashplugin approving (I've uploaded yakkety so far, I normally wait until that's approved before uploading the other releases)16:36
chrisccoulsonpitti, the procedure is basically 1) approve, 2) I verify they're ok, 3) Copy to release pocket. Not sure if that helps you though :)16:37
-queuebot:#ubuntu-release- Unapproved: casper (xenial-proposed/main) [1.376.1 => 1.376.2] (desktop-core, ubuntu-server)16:38
-queuebot:#ubuntu-release- Unapproved: juju-core (yakkety-proposed/main) [2.0~rc3-0ubuntu3.16.10.1 => 2.0~rc3-0ubuntu4.16.10.1] (ubuntu-server)16:38
pittislangasek, balloons ^ now with 10% more testing love!16:39
-queuebot:#ubuntu-release- Unapproved: accepted juju-core [source] (yakkety-proposed) [2.0~rc3-0ubuntu4.16.10.1]16:39
-queuebot:#ubuntu-release- New binary: openfoam [s390x] (yakkety-proposed/universe) [4.0+dfsg1-3] (no packageset)16:41
-queuebot:#ubuntu-release- Unapproved: indicator-network (yakkety-proposed/main) [0.8.0+16.10.20160930.5-0ubuntu1 => 0.8.0+16.10.20160930.5-0ubuntu2] (no packageset)16:41
cjwatsonlunaphyte: Yeah16:41
Laney^- fix for the live session16:41
-queuebot:#ubuntu-release- New binary: openfoam [ppc64el] (yakkety-proposed/universe) [4.0+dfsg1-3] (no packageset)16:45
pittichrisccoulson, Laney: I removed firefox ppc64el binaries; there are also some orphaned powerpc/s390x ones from 46.0.1+build1-0ubuntu1 and 47.0+build3-0ubuntu1, cleaning those too (this is why I don't like forcing without binary removal)16:45
chrisccoulsonpitti, thanks16:46
lunaphytecjwatson: thanks.  i suppose it's not necessarily kosher/supported, but your experience has been largely successful doing that?16:48
rbasaklunaphyte: please do edit https://help.ubuntu.com/community/EOLUpgrades to make it better.16:50
rbasak(you asked about adding a note?)16:50
lunaphyterbasak: oh, ok, will do16:51
rbasakLooks like you have to ask to join the team, but contributors are welcome16:51
rbasakhttps://help.ubuntu.com/community/WikiGuide16:51
rbasakThat's presumably to avoid spam.16:51
lunaphytesure, understood16:51
wxllunaphyte: or you could just become an ubuntu member and then you don't have to worry about that at all :)16:52
lunaphytewxl: hah!  that sounds like more responsibility :)16:52
wxllunaphyte: not necessarily. just need to sustain relevant contributions to the project16:53
-queuebot:#ubuntu-release- Unapproved: accepted unattended-upgrades [source] (yakkety-proposed) [0.92ubuntu1]16:53
rbasakFixing the doc sounds like a relevant but circular contribution :-)16:53
wxl!membership | lunaphyte16:53
ubot5lunaphyte: Ubuntu Membership means recognition of a significant and sustained contribution to Ubuntu and the Ubuntu community.  For more info see https://wiki.ubuntu.com/Membership/NewMember16:53
pittiLaney: indicator-network> eek16:53
lunaphytewxl: thanks16:54
pittiLaney: do any of the other unity8 upstart jobs now unexpectedly start in the unity7 session? it appears to me that this chagne needs to be replicated to all of those?16:54
wxllunaphyte: i'm on the membership board if you have other questions about it16:54
-queuebot:#ubuntu-release- Unapproved: accepted indicator-network [source] (yakkety-proposed) [0.8.0+16.10.20160930.5-0ubuntu2]16:54
cjwatsonlunaphyte: Yes, but I've been doing the general equivalent since well before Ubuntu existed so I'm not a good sample case.16:55
pittiLaney: I thought upstart had a less ugly way to do that, like start on starting DESKTOP_SESSION="unity8" or so?16:55
pittiunity-panel-service.conf:start on desktop-start DESKTOP_SESSION=ubuntu16:55
pittiLaney: ^ like this?16:56
pittiLaney: (accepted, as this is just bikeshedding, but I wonder if that affects other services too016:56
LaneyI copied it from the other job in the same source package which definitely works16:56
pittiunity-panel-service.conf:# start on started unity716:56
pittior even just that16:56
lunaphytewxl: well, i really do appreciate all of the info, but if i'm honest, it's probably not in the cards for me these days.  hopefully that doesn't come across as dismissive!16:56
LaneyI don't want to mess around at this point16:56
lunaphytecjwatson: understood, thanks16:56
wxllunaphyte: np. it will be there in the future.16:57
lunaphytegracias16:57
wxlde nada16:57
Laneymaybe you could do desktop-start DESKTOP_SESSION=... and indicator-services-start16:57
LaneySeems risky to me to experiment now16:57
pittiLaney: "start on started unity7" (like unity-panel-service.conf) seems like the equivalent of WantedBy=unity7-session.target16:58
pittiLaney: but yes, if it works, it's ok; as I said I mostly just wondered if that affects other unity8 services too16:58
LaneyIt's waiting for some event, not just that unity8 is started16:59
Laneyand I don't know - at least I haven't heard that any of those actually crash like this one does ...16:59
-queuebot:#ubuntu-release- Unapproved: thunderbird (yakkety-proposed/main) [1:45.3.0+build1-0ubuntu2 => 1:45.3.0+build1-0ubuntu3] (mozilla, ubuntu-desktop)17:00
LaneyI have something called indicator-transfer-service running, not sure if that's necessary or not17:00
Laneyseb128 / tedg: do you know if indicator-transfer is used or useful on unity 7?17:06
seb128Laney, it's not used and probably not going to be useful17:06
seb128it's supposed to indicate ongoing downloads17:06
seb128but classic apps don't use the api to talk to it17:07
seb128so probably not that useful17:07
Laneythanks17:10
LaneyI'll give it the same love, but this is lower priority17:10
tumbleweedI'm being arm twisted with beer, for some last minute universe FFes :)17:14
-queuebot:#ubuntu-release- Unapproved: ubiquity-slideshow-ubuntu (yakkety-proposed/main) [117 => 118] (kubuntu, ubuntu-desktop)17:23
-queuebot:#ubuntu-release- Unapproved: accepted thunderbird [source] (yakkety-proposed) [1:45.3.0+build1-0ubuntu3]17:25
-queuebot:#ubuntu-release- Unapproved: indicator-transfer (yakkety-proposed/main) [0.2+16.10.20160808.1-0ubuntu1 => 0.2+16.10.20160808.1-0ubuntu2] (no packageset)17:26
slangasekinfinity, pitti: do we have a target time for the start of image respins, to guide evaluating the uploads in the queue?17:29
Laneypitti: ^- same fix - this one is "just" a waste of resources17:29
slangasekI'm a waste of resources ;(17:30
Laneyurgh, there's a waste of resources in my changelog17:30
infinityslangasek: I was shooting for "very soon".  But will take another round of fixes if they don't need 4h to get through the sausage factory.17:30
infinityslangasek: I was personally waiting on the arm64 buildd kernel hack (done), and ubuntu-system-settings building successfully (in progress) and migrating.17:31
infinityI'm also curious to see what the fallout is from the firefox and thunderbird removals.17:31
infinityI bet component-mismatches explodes.17:32
slangasekinfinity: what is "soon", realistically? we have maas which is currently publishing17:32
-queuebot:#ubuntu-release- Unapproved: indicator-transfer (yakkety-proposed/main) [0.2+16.10.20160808.1-0ubuntu1 => 0.2+16.10.20160808.1-0ubuntu2] (no packageset)17:32
infinityslangasek: After that maas, since it'll beat u-s-s to the release pocket.17:32
slangasekok17:32
infinityslangasek: I dunno.  More than an hour, less than several.17:33
infinityI hope.17:33
slangasekinfinity: it seems for some reason a gdb was accepted, which is seeded everywhere and needs 4 more hours to build on armhf17:34
slangasek(appx)17:34
-queuebot:#ubuntu-release- Unapproved: rejected indicator-transfer [source] (yakkety-proposed) [0.2+16.10.20160808.1-0ubuntu2]17:34
infinityslangasek: Whee.17:34
-queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-304 [source] (yakkety-proposed) [304.132-0ubuntu1]17:34
slangasekso maybe someone wants to speak up and explain why that was accepted17:34
-queuebot:#ubuntu-release- Unapproved: accepted ubiquity-slideshow-ubuntu [source] (yakkety-proposed) [118]17:34
slangasekpitti: ?17:35
slangasekor Laney or apw or tumbleweed or stgraber ?17:35
Laneynope17:36
slangasekdoko: or did you happen to accept this gdb yourself?17:36
LaneyI accepted thunderbird though, which needs quite a while on armhf17:36
LaneyApparently the current one fails to start17:36
slangasekLaney: ah, well, thunderbird is seeded in only half the places that gdb is17:37
infinityWhich is still many places. :P17:37
Laneyblock-all source time?17:37
infinityNot all.17:37
slangasekonly ubuntu-mate, ubuntu desktop, ubuntukylin FWIW17:37
infinityBut getting close to block all seeded.17:37
slangasekoh. but also ubuntustudio + xubuntu, so that's fine17:38
slangasekinfinity, Laney: I suggest forcing thunderbird in before armhf is built, to unblock the image builds / tests on other archs and let armhf binaries catch up on their own time17:39
infinityWe'll see how the other arches fare.17:40
slangasek(since I don't think any of those projects are building armhf images currently)17:40
Laneyubuntu2/armhf actually FTBFSed17:40
LaneySo we'll see how this one does17:40
LaneyIt'll need some forcing or removals in any event since arm64/ppc64el have regressed17:42
LaneyMight be one to punt17:42
LaneyDunno how crap 38 is17:42
infinityHas anyone looked into *why* they regressed?17:42
infinityThey build fine in xenial with the same upstream version.17:43
Laneychrisccoulson: ^- (I'm guessing "no")17:45
Laneyu-s-s worked17:45
chrisccoulsoni didn't notice that ubuntu2 had been approved actually17:47
chrisccoulsonthe armhf is a race condition that we keep seeing in the build. It'll probably work fine if it's retried17:48
chrisccoulsonthe arm64 build failure is a crash when compiling the startup cache17:48
chrisccoulsonit most likely builds fine on xenial because it's not using gcc617:49
* infinity notes that gcc-5 is still in yakkety.17:52
infinityNot that that fixes the bugs, but it would defer the issue.17:52
-queuebot:#ubuntu-release- Unapproved: gcr (yakkety-proposed/main) [3.20.0-2ubuntu1 => 3.20.0-2ubuntu2] (kubuntu, ubuntu-desktop)17:54
infinitypitti: Are you on top of this indicator-transfer thing?18:03
* infinity eyes libreoffice suspiciously in the queue.18:03
-queuebot:#ubuntu-release- Unapproved: accepted gcr [source] (yakkety-proposed) [3.20.0-2ubuntu2]18:03
-queuebot:#ubuntu-release- Unapproved: accepted python-tornado [source] (yakkety-proposed) [4.4.2-1ubuntu1]18:04
-queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (yakkety-proposed) [1:20161011.1-0ubuntu1]18:06
chrisccoulsonoh, who just approved flash?18:10
-queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (precise-proposed/partner) [1:20160913.1-0ubuntu0.12.04.1 => 1:20161011.1-0ubuntu0.12.04.1] (no packageset)18:12
-queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (xenial-proposed/partner) [1:20160913.1-0ubuntu0.16.04.1 => 1:20161011.1-0ubuntu0.16.04.1] (no packageset)18:12
-queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (trusty-proposed/partner) [1:20160913.1-0ubuntu0.14.04.1 => 1:20161011.1-0ubuntu0.14.04.1] (no packageset)18:12
infinitychrisccoulson: Moi.18:12
chrisccoulsoninfinity, ah, thanks. I've just uploaded the rest of them now :)18:12
-queuebot:#ubuntu-release- Unapproved: gnome-settings-daemon (yakkety-proposed/main) [3.22.0-1ubuntu1 => 3.22.1-0ubuntu1] (ubuntu-desktop)18:34
slangasekjbicha: ^^ this impacts images across 4 flavors, for which image spins are supposed to start imminently; why is it uploaded now?18:35
jbichaslangasek: it can be an SRU right?18:36
slangasekjbicha: if it meets SRU requirements; ok I see the SRU template in the one bug, thanks18:37
jbichait's not needed in the release images18:38
slangasekjbicha: I'm asking because it's hard to coordinate across all the release team working the queue in parallel, so it's important to have clarity about the target for these uploads18:38
slangasekok18:38
flexiondotorginfinity, Is the release going to be delayed?19:00
infinityflexiondotorg: I shouldn't think so.19:01
flexiondotorgOK19:01
flexiondotorgThe rumour mill is speculating. I'll pour water on that.19:01
infinityflexiondotorg: Rumour mills are special.19:01
flexiondotorgIndeed.19:02
infinityflexiondotorg: Perhaps the rumour mill should be harder at work on testing, reporting, and fixing. :P19:03
flexiondotorgThat too.19:03
lunaphytethanks everyone for entertaining my questions, etc.19:19
slangasekdoes a binary removal of an arch: all package on a specific arch DTRT? :P19:21
infinityslangasek: no.19:22
slangasekok cool19:22
slangasekso how do we get juju in?19:22
slangasekI guess I can 'force' it19:22
infinityNo.19:23
slangasekinfinity: I hope you're planning on elaborating / presenting an alternative :)19:24
infinityI'm looking at the situation first.19:24
slangasekok19:24
slangaseksummary from my side: juju dropped 32-bit arch supports, with my sign-off; no transitional packages for this in yakkety because the drop is retroactive to xenial so for 16.10 we just want the packages gone; in the process that means juju is migrating from an (uninstallable) arch: all package to an arch: some package; and britney doesn't want to let it in19:25
infinityCheck, and rmadison confirms.19:25
slangasekand I guess, from the output, that the arch: all-> arch: some change was made only in the latest release, since previous release was getting autopkgtest results19:26
infinityOkay, in that case, your propose arch-some removal might work.19:26
slangasekok19:26
infinityThe reason I said it doesn't is because all copies in LP are source-based, so binary removals always come back.19:26
slangasekdid that, let's see what happens - thanks19:26
infinityAnd, thus, should be avoided.19:26
infinity(And definitely avoided for arch:all, which is just confusing)19:26
infinityBut as a temp solution, it might DTRT.19:27
infinityIf it doesn't, just remove juju from the release pocket entirely.19:27
infinityStill beats a force.19:27
infinityOkay, and juju's not in any metapackages, so don't need a refresh.19:32
infinityThough after the current things all settle, I'll do a world refresh of meta locally to see if any changes got missed.19:32
pittislangasek: I didn't accept it; it seemed a bit dubious/too intrusive to me19:37
-queuebot:#ubuntu-release- Unapproved: wine-development (yakkety-proposed/universe) [1.9.19-1ubuntu1 => 1.9.20-1ubuntu1] (no packageset)19:37
-queuebot:#ubuntu-release- Unapproved: accepted wine-development [source] (yakkety-proposed) [1.9.20-1ubuntu1]19:37
pittiinfinity: do you want everyone else to stay away from unapproved now?19:38
pittior still want me to review the indicator-transfer thing?19:38
pitti(I have a hunch that's going to be needed for the ubuntu desktops at least, but not blocking all other flavors)19:38
pittiurgh, a LibO upload?19:39
pittidear http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt, pretty please update19:39
infinitypitti: GO ahead and sort that, please.19:39
pittiLaney: running these shell scripts is a nice waste of resources too, but hopefully a bit less :)19:40
-queuebot:#ubuntu-release- Unapproved: accepted indicator-transfer [source] (yakkety-proposed) [0.2+16.10.20160808.1-0ubuntu2]19:41
pittijbicha: do you want that g-s-d on the images? diff looks sane enough to me, but at this point there's little margin for errors19:42
pittijbicha: did you test this on real hw with a battery? screen saver works ok?19:43
jbichapitti: did you see s_langasek's comment above about it ^19:43
pittino, /me reads backscroll19:43
pittimeh, somehow my firefox/ppc64el removal didn't work?19:44
jbichaI'd rather g-s-d just be an SRU actually; the bug fixes in it are fairly minor19:45
pittiack, they don't seem image-critical, unlike the indicator thing19:45
pitti(relevant for live image)19:45
pittiinfinity: I guess you should put a propagation block in place now, so that we have more control over this?19:46
infinitypitti: Yeahp.  Doing that now.19:46
pittiinfinity, slangasek: are you on top of the juju 32 bit removals so that this can land, or want me to?19:46
infinitypitti: Steve's on the juju case.19:46
pittithe transitional moved from arch: all to arch: [list]19:46
pittiack19:46
pittiinfinity: so I can deal with firefox; 46.x and 47.x are gone, but 48.x ppc binaries still exist19:47
infinitypitti: The easier way to do that is just to remove source package by version.19:47
infinitypitti: remove-package -e 48.blah firefox19:47
infinitypitti: Way simpler than trying to hunt down the mismatched bits.19:48
pittiinfinity: that would entirely remove it from yakkety for a short blip of time, though?19:48
infinitypitti: Do you care?19:48
pittiI ran http://paste.ubuntu.com/23309737/ earlier, apparently that didn't work19:48
infinityIf the goal is to get 49 in ASAP.19:48
pittiok19:48
pittiinfinity: done19:49
infinitypitti: I'm more worried about c-m exploding due to this.19:49
pittiseems a bit awkward to remove "good" binaries temporarily from the release, but indeed, better than screwing it up for another publisher19:49
infinitypitti: But maybe with archive-reorg, it won't.  The old "if we have no firefox, other browsers get yanked into main" thing *might* have been a build-dep issue.19:50
infinityHere's hoping.19:50
infinityI honestly don't recall if it was build-dep or runtime.19:50
infinityThough, at the very least, we'll need a meta refresh.19:50
infinityWhich is on my TODO in a publisher cycle or three.19:51
pittiinfinity: after it updates, http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt will still have some remaining bits -- e. g. libnuma1 on s390x only19:51
infinityI'll hold off on the britney block for another cycle or two as well.19:51
pittioh wait, libnuma1 will then be in "optional" everywhere19:51
infinityI thought I had a hint for numa.19:51
pittiI was going to ask whether it's ok to have a different priority on a particular arch only19:51
pittibut seems it's the other way round -- it currently differs, this will now make it equal to other arches19:52
infinityYou can't have mismatched priorities on arches, LP doesn't allow it.19:52
infinityUnless something goofs up.19:52
infinityDoes architecture-mismatches show an issue?19:52
pittiah no - libnuma1 is in standard for other arches19:52
pittipython* and perl* should be gone now -- I figure we need to promote this silly pinentry-curses now19:53
pittiinfinity: wow, I was completely ignorant of http://people.canonical.com/~ubuntu-archive/architecture-mismatches.txt19:53
infinityI'll clean up the mismatches.19:53
infinitySo we don't stomp on each other.19:53
pittiack -- i. e. promote unity on arm64?19:54
infinityAnd priority stuff as well.19:54
pittiinfinity: wait19:54
pittiinfinity: can you predict what it's going to look like? or were you just going to promote pinentry-curses?19:55
infinitypitti: I'm fixing libnuma with a hint.  pinentry probably will want to promote.  But also waiting for the perl stuff to fall out.19:56
pittilibnettle6 might be a transient dep of pinentry19:56
infinitypitti: numa fix committed.19:56
infinityAnd unity8 fixed.19:57
infinityFinishing my lunch while I way for some archive settle.19:58
tyhicksHi20:02
tyhickswe've just discovered that some confined programs are being denied access to the system bus due to the resolved changes in yakkety20:02
tyhicksat least tcpdump and ntpd are affected20:03
pittithat sounds SRUable?20:03
tyhicksnss seems to be falling back to do traditional name lookups whenever apparmor denies access to the bus but I don't know if that's acceptable20:03
tyhickspitti: you would know best if the fallback is "safe" ^20:03
pittityhicks: NSS in general does work; you mean for apparmor profiles of programs where NSS doesn't work?20:04
pittityhicks: it's "safe" in yakkety as we disabled DNSSEC (and thus enforcement), so ATM falling back to "dns" is only a convenience/longer timeout/no caching issue20:04
pittityhicks: and desktops use dnsmasq anyway (again), not resolved20:05
tyhickspitti: ok, so it sounds like we can fix this in an SRU20:05
pittityhicks: so you mean tcpdump/ntpd do lookups via NSS and are being denied D-Bus access?20:05
tyhickspitti: correct20:05
pittiok20:05
sarnold.. and everything else that aa-status reports as confined20:06
pittityhicks: i_nfinity installed a propagation block now, so we should actaully be able to start SRU uploads now20:06
pittior rather, "soon" (block not yet active)20:07
tyhickspitti: do I need to explicitly upload to yakkety-updates or will they be automatically routed to -updates?20:07
pittityhicks: no, *don't* upload to -updates, we need to reject this (and make sure we actually spot it)20:07
pittityhicks: continue to upload to yakkety or yakkety-proposed20:07
tyhicksthanks20:08
pittityhicks: -proposed is the same for devel and SRUs, just the propagation changes from -release to -updates20:08
tyhicksack20:08
pittiso, uploading is fine at all times, but I can only review it after we get a release block20:08
infinitypitti: Yeah, the block will be in a couple of cycles, I don't want to block just to unblock everything in there right now.20:11
* pitti waves good night20:13
-queuebot:#ubuntu-release- Unapproved: strongswan (trusty-proposed/main) [5.1.2-0ubuntu2.4 => 5.1.2-0ubuntu2.5] (no packageset)20:15
-queuebot:#ubuntu-release- Unapproved: multipath-tools (trusty-proposed/main) [0.4.9-3ubuntu7.14 => 0.4.9-3ubuntu7.15] (core)20:17
-queuebot:#ubuntu-release- Unapproved: unattended-upgrades (xenial-proposed/main) [0.90 => 0.90ubuntu0.1] (desktop-core, ubuntu-server)20:17
brendandwho do i need to nudge to get cloud-init moving along from -proposed (in xenial)?20:32
-queuebot:#ubuntu-release- Unapproved: flashplugin-nonfree (yakkety-proposed/multiverse) [11.2.202.635ubuntu1 => 11.2.202.637ubuntu1] (no packageset)20:32
-queuebot:#ubuntu-release- Unapproved: accepted flashplugin-nonfree [source] (yakkety-proposed) [11.2.202.637ubuntu1]20:34
-queuebot:#ubuntu-release- Unapproved: icinga (xenial-proposed/universe) [1.13.3-2 => 1.13.3-2ubuntu0.1] (no packageset)20:35
wxlwe having a respin at some point?20:35
valorieI heard "More than an hour, less than several"20:36
wxljj20:36
wxler20:36
wxls/j/k/g20:36
valorielol20:36
=== nacc_ is now known as nacc
brendandinfinity, any chance of nudging the cloud-init (xenial) sru along? bugs are verified, it's aged a week, and it's hurting us badly. understand if you're busy though20:42
slangasekvalorie, wxl: right, and that was 3 hours ago20:47
slangasekinfinity: what's the long pole now?20:47
acheronukwaiting until migration blocks are in place so I thought I read?20:48
infinityslangasek: Waiting on firefox migration, at least.20:52
infinityLess convinced about what to do with thunderbird.20:53
infinityOh, but it looks like it's built/failed everywhere it's going to.20:53
infinitySo maybe we can nudge that along too.20:53
infinityBut yeah, probably time for the block and unblocks.20:55
infinityDoing that now.20:55
* valorie sends a thousand {{{{{{{{{{{{{{{{{{{{{{hugs}}}}}}}}}}}}}}}}}}}}}}}}}} to the release team20:56
infinityI only deal in pie.20:56
* valorie adds pie20:57
valorieand beer20:57
valorieand whisky for those who want it20:58
* wxl wants maté20:58
valoriesome nice cider for those who don't20:58
cjwatsoninfinity: priorities> LP allows it, we just try to avoid it because it's a pain to keep track of.  Maybe you're thinking of dak.20:58
infinitycjwatson: Perhaps.20:59
acheronukvalorie: I suspect strong coffee is also required20:59
infinitycjwatson: The archive doesn't allow it, then. :P20:59
valorieI'm willing to bet the team has laid in stores of coffee AND tea21:00
dannfinfinity: i'm not sure how to report this via the QA tracker (is that setup yet?), but arm64 ISOs need a fix - LP: #163247321:09
ubot5Launchpad bug 1632473 in Ubuntu CD Images "arm64 grub needs to load gzio" [Undecided,New] https://launchpad.net/bugs/163247321:09
infinitydannf: Is this already correct in the mini.iso?21:14
infinitydannf: Cause I see no mention of gzio in d-i...21:15
dannfinfinity: checking21:17
dannfinfinity: mini iso boots - seeing if i can figure out why - side-effect perhaps?21:17
infinitySide effect of what? :P21:18
dannfsome other preloaded module perhaps21:18
infinityThe grub.cfg on mini.iso is pretty sparse.21:21
dannfhrm.. w/ debug=all, i don't see gzio ever load.21:21
dannfinfinity: ah - looks like the kernel on the iso is a gzip'd file w/ no UEFI stub21:24
dannfwhereas on the mini.iso, it's a gzip's kernel w/ a UEFI stub prefix like it should be21:24
infinity*raise brow*21:26
infinityThat seems suboptimal.21:27
infinitySo, I get vmlinuz straight out of d-i.21:28
infinityWhy are you giving me two different kernels? :P21:28
dannfindeed...21:30
dannfoh - i'm not. i was just apparently testing the wrong mini.iso! egg/face21:34
infinityAhh, so d-i is also broken?  That's less confusing.21:34
dannfyes. fixing.21:35
infinityRight, do some test runs there to get something that works, and I can mirror it in debian-cd, if it's not just carried over in cd-info.tar.gz.21:35
infinitydannf: A little late for grub uploads now, but I'd suggest that, perhaps, if gzio is required for arm64 now, it should probably be built-in. :P21:36
infinity(I assume it is for x86?)21:37
infinityOh, hrm.  Won't this also break the installed system on reboot?21:37
infinityOh, no, looks like the installed grub.cfg has gzio just in case.21:38
dannfyeah - i've been booting compressed kernels for a while  on EFI systems w/ no problem21:59
cyphermoxdannf: infinity: it's already builtin to the EFI images22:15
dannfinfinity, cyphermox : https://code.launchpad.net/~dannf/debian-installer/lp1632473/+merge/30819922:19
infinitydannf: Please commit, tag, and upload.22:20
dannfinfinity: ack22:20
-queuebot:#ubuntu-release- Unapproved: debian-installer (yakkety-proposed/main) [20101020ubuntu482 => 20101020ubuntu483] (core)22:29
flexiondotorginfinity, Just trying to organise some final MATE testing.22:35
flexiondotorgIs a world respin planned?22:35
wxlsupposedly incoming soon flexiondotorg22:36
flexiondotorgwxl For world?22:36
sarnoldflexiondotorg: perhaps define what you mean by "world respin"22:37
flexiondotorgAll the flavours.22:37
flexiondotorgHaving images recreated.22:37
slangasekthe world is constantly spinning, no "re" required22:41
slangasekyes, all flavors need an updated image22:41
slangasekstokachu, balloons, cyphermox: so, juju-core autopkgtest failure on ppc64el due to manual provider? expected?22:41
cyphermoxI hear it's expected, but needs to be fixed?22:43
cyphermoxslangasek: also, what do you mean, the world is spinning? isn't it constantly accelerating upwards at 9.8m/s^2?22:44
slangasekcyphermox: what does "needs to be fixed" mean here?  Should I expect a new fixed package before release?22:56
cyphermoxslangasek: we discussed changes to this test this morning, but I don't know if you should be expecting a fixed package now22:57
cyphermoxballoons: ^22:57
-queuebot:#ubuntu-release- Unapproved: update-notifier (xenial-proposed/main) [3.168.1 => 3.168.2] (ubuntu-desktop, ubuntu-server)22:59
* tsimonq2 buys the release team a virtual cup of coffee and/or Red Bull for whoever wants it 23:22
cyphermoxtsimonq2: good plan. I took a short video games break ... and it ended in a game over :(, but now coffee seems in order23:55
tsimonq2cyphermox: cheers :)23:55

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