=== valorie is now known as valorie_
=== valorie_ is now known as valorie
[03:51] <pitti> santa_: indeed; calligra released
[04:26] <valorie> pitti: \o/ and thanks!
[06:08] -queuebot:#ubuntu-release- Unapproved: accepted python-pylxd [source] (xenial-proposed) [2.0.5-0ubuntu1.1]
=== Mirv_ is now known as Mirv
=== caribou_ is now known as caribou
[11:58] <xnox> slangasek, i have built-using better handling... however I'm not sure it's great
[11:58] <xnox> ? Unknown dependency libc6-mips32 (= 2.24-0ubuntu1) by zsh-static
[11:58]  * xnox giggles
[11:58] <xnox> maybe we can specify something on the source package, that if something is built-using me it means this binary package?
[12:00] <xnox> e.g. Source: glibc would have Built-Using-Binary-Hint: libc6-dev, or libc6-dev should Built-Using-Binary-Hint: True
=== ara is now known as Guest69211
[12:53] <mardy> pitti: the armhf task seems to be stuck here, can you please restart it? https://bileto.ubuntu.com/#/ticket/1971
[12:54] <mardy> (britney)
=== s8321414_ is now known as s8321414
[13:07] <xnox> infinity, slangasek: what do you think about http://people.canonical.com/~xnox/germinate-output/builtusing/desktop.depends ?
[13:07] <xnox> grep for "Built-Using"
[13:10] -queuebot:#ubuntu-release- Unapproved: fcitx (xenial-proposed/main) [1:4.2.9.1-1ubuntu1 => 1:4.2.9.1-1ubuntu1.16.04.1] (input-methods, kubuntu, ubuntu-desktop)
=== RAOF_ is now known as RAOF
[13:19] <xnox> infinity, we have name =)
[13:21] <apw> xnox, yay ... i think he is afk just at this instance collecting supplies or similar
=== s8321414_ is now known as s8321414
[13:42] <acheronuk> Zesty Zapus
=== coreycb` is now known as coreycb
[14:09] <pitti> mardy: will do shortly; I need to update request.cgi to the new PPA naming forat
[14:12]  * barry will forever read "zapus" as "zappa"
[14:15] <davmor2> barry: just call it frank for short
[14:16] <flocculant> lol
[14:17] <barry> davmor2: +1
[14:18] <mardy> pitti: thanks
[14:21] <tsimonq2> WOOOOOO
[14:21] <tsimonq2> Z announced!
=== infinity changed the topic of #ubuntu-release to: Released: Trusty 14.04.5, Xenial 16.04.1, Yakkety 16.10 | Archive: closed | Zesty Release Coordination | Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release team | We accept payment in cash, check or beer | melior malum quod cognoscis
[14:21] <pitti> OMG!
[14:22] <tsimonq2> IKR ZOMGWTFBBQ!1
[14:22]  * infinity is grabbing a bit of breakfast, then spending the day opening ZZ Top.
[14:22] <pitti> dictionary o'clock
[14:22] <flocculant> frank is better than zz top
[14:23] <pitti> infinity: not Zany, Zesty
[14:23] <infinity> pitti: Yes, you're reading the topic diff backwards.
[14:23] <infinity> 08:21 -!- Irssi: Topic: -: Zany Release Coordination
[14:23] <infinity> 08:21 -!- Irssi: Topic: +: Zesty Release Coordination
[14:23] <pitti> indeed, yes
[14:24] <infinity> (best irssi plugin ever)
[14:25] <pitti> ok, so a zapus is a tiny mouse, but in my dictionary "zesty" is a culinary term (like "well spiced").. cruel!
[14:25] <flocculant> pitti: red in tooth and claw :p
[14:26] <infinity> Zesty can also be applied to people (and anthropomorphic animals, I guess) to mean something similar to feisty.  So, I guess we have a repeat.
[14:26] <apw> and cna mean full of intersting flavours and depth
[14:26] <infinity> But at least 99% of our uploaders can probably spell this one.
[14:26] <flocculant> pitti: zest - great enthusiasm and energy
[14:27] <apw> lots of fun meanings, but most importantly, easy to spell
[14:27] <pitti> indeed, http://dict.leo.org/?search=zest is more helpful :)
[14:27] <flocculant> :)
[14:27] <infinity> I'll bet most can pronounce it too, which will be novel.
[14:27] <flocculant> ha ha
[14:34] <xnox> slangasek, i have germinate patch and components missmatches patch
[14:34] <xnox> but it's impossible for me to run components-missmatches because the output of my germinate is not what it wants/expects.
[14:34] <xnox> what shall I do?
[14:34] <xnox> push germinate & ubuntu-archive-tools to launchpad and ask you to pull those and run them on snakefruit or something? did you manage to run components-missmatches last time?
[14:46] <pitti> mardy: done
[14:49] <pitti> infinity: btw, can https://launchpad.net/ubuntu/wily finally stop being "supported"?
=== maclin1 is now known as maclin
[14:59] <mardy> pitti: thanks!
[15:07] <pitti> Laney: pushed https://git.launchpad.net/~ubuntu-release/+git/autopkgtest-cloud/commit/?id=79e2071e05 but creating containers and nova images is blocked on actually opening the release on archive.u.c.
[15:08] <infinity> pitti: Working on it. :P
[15:08] <pitti> Laney: running seed-new-release for autopkgtest now, and making some tweak to it to not take so hilariously long
[15:08] <pitti> infinity: sorry, wasn't meant as impatience, just a status update
[15:17] <slangasek> xnox: what do I think> I think it's a big text table ;)  and previously I ran patched germinate locally for testing c-m output, I think I posted my hacked-up script for this on the mailing list at the time
[15:24] <slangasek> tjaalton: freeipa removed by mistake> I guess the mistake here was processing the removal from unstable, but the package was still in experimental at the time which was where the Ubuntu version had been synced from?  Yeah, seems I should've been reading more closely. :/  As far as getting it back into yakkety, is that important enough to do for a non-LTS release, vs. picking it back up in zesty?
[15:26] <tjaalton> slangasek: well, some folks seem to want the client at least. the "orphaned" xenial version will still work after upgrade to yakkety
[15:27] <tjaalton> maybe I could provide it via the ppa
[15:38] <slangasek> tjaalton: if you think it's important, we /can/ push it into -updates; I'm just pondering the best way to do this
[15:39] <slangasek> I don't want to pull in the current version of the package from Debian unstable without it first being tested
[15:39] <slangasek> but I could resurrect the binaries that were previously in yakkety and copy them to yakkety-proposed
[15:39] <slangasek> and I would forego any SRU verification in this case
[15:39] <slangasek> forgo
[15:59] <tsimonq2> infinity: when you set up Zesty in Launchpad, I'll do the wiki pages, unless you want me to do it now?
[16:00] <infinity> tsimonq2: Which wiki pages were you intending to set up?
[16:00] <tsimonq2> w.u.c/ZestyZapier
[16:01] <tsimonq2> whoops, Zapus
[16:03] <tsimonq2> infinity: ^
[16:04] <tsimonq2> The ones I called dibs on a few days ago. :P
[16:05] <tjaalton> slangasek: resurrecting them is fine, and i'll let folks test them too
[16:15] <slangasek> tjaalton: well, I'm going to resurrect directly to yakkety-updates :)
[16:16] <slangasek> tjaalton: except, erm, copy-package isn't showing me binaries for 4.3.2-1
[16:17] <apw> would we have cleaned -release before closing it
[16:17] <slangasek> apw: not out of launchpad's guts
[16:18] <slangasek> though maybe there was a launchpad cleaning I'm just not aware of
[16:18] <slangasek> it did get copied to release, so it definitely had binaries at one point ;)
[16:19] <slangasek> tjaalton: so since copy-package fails me, it'll have to go through the SRU process (because there will be new binary builds, that need to be tested before publish to -updates, so SRU bug + verification)
[16:20] <cjwatson> We haven't purged binaries from LP for quite a while
[16:21] <cjwatson> You may have better luck if you give copy-package an explicit version?
[16:21] <cjwatson> (if you didn't already)
[16:21] <cjwatson> Oh
[16:21] <cjwatson> This is just copy-package lying to you, actually
[16:21] <cjwatson> IIRC there's some reason it fails to accurately predict what the copy will contain in this case
[16:21] <cjwatson> But it's just an inaccurate prediction, it doesn't mean that binaries won't be copied
[16:22] <cjwatson> slangasek: It's a safe copy, there'll be no new binary builds (can't - LP would reject them)
[16:24] <slangasek> cjwatson: ah, ok
[16:25] <slangasek> tjaalton: in that case, resurrected to yakkety-updates, maybe :)
[16:39] <infinity> slangasek: copy-package won't show binaries.
[16:39] <infinity> slangasek: Oh, Colin explained it.
[16:40] <infinity> Well, "explained". :)
[16:41] <infinity> cjwatson: The "some reason" is that copy-package uses getPublishedBinaries, I assume.
[16:41] <infinity> cjwatson: And, well, that ain't published.
[16:41] <infinity> s/that/they/
[16:42] <infinity> Yup, it sure does.
[16:42] <infinity> Not sure if there's a better way to make that prediction more reliably.
[16:42] <infinity> But it's a wart we all learn of and then learn to not care about.
[16:42] <cjwatson> Indeed.
[16:43] <infinity> I guess the "better" way would be to follow from the source to the builds to the builds' binaries, but ick.
[16:47] <tjaalton> slangasek: sweet, thanks :)
[16:47] <infinity> tsimonq2: Anyhow, feel free to create whatever boilerplate zesty wiki pages should exist, except for the release schedule.  I'll get to that shortly.
[17:18] <krytarik> pitti, infinity: Now that the new Calligra package (and thus Krita) is in yakkety-updates, can one of you please update the Studio meta again too?  Thanks!
=== med_` is now known as medberry
[19:09] <pitti> infinity: want me to do the distro-info SRUs? (out of self-interest, I need it for the infra)
[19:09] <pitti> stefanor didn't commit the update to https://anonscm.debian.org/git/collab-maint/distro-info-data.git yet, but being collab-maint I suppose I could do that too
[19:13] <pitti> bah, the yakkety release date in distro-info-data is one week off
[19:17] <pitti> https://anonscm.debian.org/git/collab-maint/distro-info-data.git updated
[19:21] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (yakkety-proposed/universe) [0.7ubuntu1 => 0.8+16.10ubuntu1] (no packageset)
[19:24] -queuebot:#ubuntu-release- Unapproved: distro-info-data (yakkety-proposed/main) [0.29 => 0.29ubuntu0.1] (core)
[19:25] -queuebot:#ubuntu-release- Unapproved: distro-info-data (xenial-proposed/main) [0.28ubuntu0.1 => 0.28ubuntu0.2] (core)
[19:27] -queuebot:#ubuntu-release- Unapproved: distro-info-data (trusty-proposed/main) [0.18ubuntu0.5 => 0.18ubuntu0.6] (core)
[19:27] <pitti> infinity: ^ review, s'il te plaît ?
[19:28] -queuebot:#ubuntu-release- Unapproved: distro-info-data (precise-proposed/main) [0.8ubuntu0.10 => 0.8ubuntu0.11] (ubuntu-server)
[19:34] <barry> i know the zesty archive is closed.  can i still do an upload and have it sit around until it opens, or should i wait.  and if the latter, what's the eta?
[19:35] <pitti> barry: you can't upload yet, it hasn't been created on https://launchpad.net/ubuntu/ yet
[19:35] <barry> pitti: ack
[19:40] <tumbleweed> pitti: oh, sorry. was on a plane on thursday :P
[19:40] <pitti> tumbleweed: o/
[19:40] <pitti> tumbleweed: no worries; I hope you don't mind my commits?
[19:40] <tumbleweed> go for it :)
[19:40] <pitti> tumbleweed: retroactively done :) (I wanted it in collab-maint before uploading the SRUs)
[19:41] <pitti> I just didn't upload, I don't want to do that without maintainer's consent at least
[19:41] <tumbleweed> yeah, I'll do that now
[19:41] <pitti> barry: I also wonder where to put my debhelper merge :)
[19:42] <tumbleweed> oh, he only announced the new name today, anyway
[19:54]  * barry 's finger hovers over the button
[19:57] -queuebot:#ubuntu-release- Unapproved: criu (xenial-proposed/universe) [2.0-2ubuntu3 => 2.6-1ubuntu1~ubuntu16.04.1] (no packageset)
=== med_ is now known as Guest62846
[20:11] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.16 => 2.16ubuntu1] (desktop-core, ubuntu-server)
[20:13] -queuebot:#ubuntu-release- Unapproved: snapd (yakkety-proposed/main) [2.16+16.10ubuntu1 => 2.16+16.10ubuntu1.1] (desktop-core, ubuntu-server)
[21:21] -queuebot:#ubuntu-release- Unapproved: debian-installer (xenial-proposed/main) [20101020ubuntu451.6 => 20101020ubuntu451.7] (core)
[21:33] -queuebot:#ubuntu-release- Unapproved: debian-installer (trusty-proposed/main) [20101020ubuntu318.40 => 20101020ubuntu318.41] (core)
[21:56] <clivejo> hi folks, we (Kubuntu) have a very small fix to make to our packaging, but it is actually preventing our users from upgrading to Yakkety.  We have fixed the packaging and have a debdiff on this bug report LP 1633692
[21:56] <ubot5`> Launchpad bug 1633692 in plasma-discover (Ubuntu Xenial) "missing depends on ubuntu-release-upgrader-qt - breaks GUI upgrades to yakkety" [Critical,Confirmed] https://launchpad.net/bugs/1633692
[21:57] <clivejo> anyone able to help get it accepted and into Xenial ASAP?
[22:15]  * ahoneybun pokes Mirv
[22:17] <tsimonq2> clivejo: You just need to upload it, and it will go in the SRU queue.
[22:55] -queuebot:#ubuntu-release- New: accepted squashfuse [source] (xenial-proposed) [0.1.100-0ubuntu1~ubuntu16.04.1]
[22:56] -queuebot:#ubuntu-release- New binary: squashfuse [amd64] (xenial-proposed/none) [0.1.100-0ubuntu1~ubuntu16.04.1] (no packageset)
[22:56] -queuebot:#ubuntu-release- New binary: squashfuse [ppc64el] (xenial-proposed/none) [0.1.100-0ubuntu1~ubuntu16.04.1] (no packageset)
[22:56] -queuebot:#ubuntu-release- New binary: squashfuse [i386] (xenial-proposed/none) [0.1.100-0ubuntu1~ubuntu16.04.1] (no packageset)
[22:56] -queuebot:#ubuntu-release- New binary: squashfuse [s390x] (xenial-proposed/none) [0.1.100-0ubuntu1~ubuntu16.04.1] (no packageset)
[22:57] -queuebot:#ubuntu-release- New binary: squashfuse [arm64] (xenial-proposed/none) [0.1.100-0ubuntu1~ubuntu16.04.1] (no packageset)
[22:57] -queuebot:#ubuntu-release- New binary: squashfuse [powerpc] (xenial-proposed/none) [0.1.100-0ubuntu1~ubuntu16.04.1] (no packageset)
[22:57] -queuebot:#ubuntu-release- New binary: squashfuse [armhf] (xenial-proposed/none) [0.1.100-0ubuntu1~ubuntu16.04.1] (no packageset)
=== tsimonq2 is now known as simon-says
=== simon-says is now known as tsimonq2