[00:10] -queuebot:#ubuntu-release- Unapproved: icingaweb2 (xenial-proposed/universe) [2.1.0-1ubuntu1.1 => 2.1.0-1ubuntu1.2] (no packageset)
[00:11] -queuebot:#ubuntu-release- Unapproved: zend-framework (xenial-proposed/universe) [1.11.11-0ubuntu3 => 1.11.11-0ubuntu3.16.04.1] (no packageset)
[00:12] -queuebot:#ubuntu-release- Unapproved: zend-framework (yakkety-proposed/universe) [1.11.11-0ubuntu3 => 1.11.11-0ubuntu3.16.10.1] (no packageset)
[00:29] -queuebot:#ubuntu-release- Unapproved: tomcat8 (xenial-proposed/main) [8.0.32-1ubuntu1.2 => 8.0.32-1ubuntu1.3] (kubuntu, ubuntu-desktop, ubuntu-server)
[00:38] -queuebot:#ubuntu-release- Unapproved: tomcat8 (yakkety-proposed/main) [8.0.37-1 => 8.0.37-1ubuntu0.1] (kubuntu, ubuntu-desktop, ubuntu-server)
[00:57] <nacc> slangasek: can you reject those tomcat8 uploads? i am going to try and include an additional bugfix
[03:49] -queuebot:#ubuntu-release- New binary: node-ebnf-parser [amd64] (zesty-proposed/universe) [0.1.10+dfsg-3build1] (no packageset)
[03:54] -queuebot:#ubuntu-release- New binary: node-lex-parser [amd64] (zesty-proposed/universe) [0.1.4-5build1] (no packageset)
[04:17] -queuebot:#ubuntu-release- New binary: node-levn [amd64] (zesty-proposed/universe) [0.3.0+dfsg-1build1] (no packageset)
[04:17] -queuebot:#ubuntu-release- New binary: node-prelude-ls [amd64] (zesty-proposed/universe) [1.1.2+dfsg-2build1] (no packageset)
[04:20] -queuebot:#ubuntu-release- New binary: node-optionator [amd64] (zesty-proposed/universe) [0.8.2+dfsg-1build1] (no packageset)
[04:27] -queuebot:#ubuntu-release- New binary: node-type-check [amd64] (zesty-proposed/universe) [0.3.2+dfsg-1build1] (no packageset)
[04:42] -queuebot:#ubuntu-release- New binary: node-livescript [amd64] (zesty-proposed/universe) [1.5.0+dfsg-3build1] (no packageset)
[04:45] -queuebot:#ubuntu-release- New binary: node-jison [amd64] (zesty-proposed/universe) [0.4.17+dfsg-3build1] (no packageset)
[05:06] <slangasek> nacc: done
[05:06] -queuebot:#ubuntu-release- Unapproved: rejected tomcat8 [source] (xenial-proposed) [8.0.32-1ubuntu1.3]
[05:07] -queuebot:#ubuntu-release- Unapproved: rejected tomcat8 [source] (yakkety-proposed) [8.0.37-1ubuntu0.1]
[05:22] -queuebot:#ubuntu-release- New binary: libjs-jquery-jstree [amd64] (zesty-proposed/universe) [3.3.3+dfsg1-1] (no packageset)
[05:26] -queuebot:#ubuntu-release- New binary: golang-github-googleapis-proto-client-go [amd64] (zesty-proposed/universe) [0.0~git20160726.0.e5790fe-1] (no packageset)
[06:25] -queuebot:#ubuntu-release- Unapproved: evolution-data-server (yakkety-proposed/main) [3.22.1-0ubuntu2 => 3.22.3-0ubuntu0.1] (ubuntu-desktop)
[06:37] -queuebot:#ubuntu-release- Unapproved: evolution (yakkety-proposed/universe) [3.22.1-0ubuntu2 => 3.22.3-0ubuntu0.1] (ubuntugnome, ubuntukylin)
[06:40] <tjaalton> could someone let mesa finally migrate to zesty main, it's still stuck in proposed because plasma-framework tests on s390x are failing
[06:40] <tjaalton> now that all the other tests are fine
[07:21] -queuebot:#ubuntu-release- Unapproved: evolution (yakkety-proposed/universe) [3.22.1-0ubuntu2 => 3.22.3-0ubuntu0.1] (ubuntugnome, ubuntukylin)
[07:54] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-57.78] (core, kernel)
[07:54] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-57.78~14.04.1] (kernel)
[08:26] -queuebot:#ubuntu-release- New sync: kdesvn (zesty-proposed/primary) [2.0.0-1]
[08:42] -queuebot:#ubuntu-release- New binary: zconfig [amd64] (zesty-proposed/universe) [3.1.0-1] (zope)
[10:36] <rbasak> apw, bdmurray: there's no SRU information in bug 1625072. I'm not sure what to check has been tested before releasing, since there's no test plan, and I don't know if a test plan has been considered or accepted by the SRU team.
[10:36] <ubot5`> bug 1625072 in lttng-modules (Ubuntu Yakkety) "lttng-modules 2.8.0-1 ADT test failure with linux 4.8.0-11.12" [Undecided,Fix committed] https://launchpad.net/bugs/1625072
[10:41] <rbasak> infinity, dannf: for bug 1633629, shouldn't we be doing some testing of other architectures to make sure that we aren't regressing something?
[10:41] <ubot5`> bug 1633629 in debian-installer (Ubuntu Yakkety) "arm64: KASLR breaks MODVERSIONS" [Undecided,Fix committed] https://launchpad.net/bugs/1633629
[11:15] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (trusty-proposed) [2.0.0+dfsg-2ubuntu1.31]
[11:19] -queuebot:#ubuntu-release- Unapproved: rejected pulseaudio [source] (trusty-proposed) [1:4.0-0ubuntu11.2]
[11:27] -queuebot:#ubuntu-release- Unapproved: accepted zend-framework [source] (xenial-proposed) [1.11.11-0ubuntu3.16.04.1]
[11:30] -queuebot:#ubuntu-release- Unapproved: rejected icingaweb2 [source] (xenial-proposed) [2.1.0-1ubuntu1.2]
[11:37] -queuebot:#ubuntu-release- Unapproved: accepted nautilus [source] (xenial-proposed) [1:3.18.4.is.3.14.3-0ubuntu6]
[12:06] <sil2100> Hello! Could anyone from the SRU team take a look at the xenial and yakkety dbus uploads?
[12:32] -queuebot:#ubuntu-release- Unapproved: partman-btrfs (xenial-proposed/main) [18ubuntu1 => 18ubuntu1.1] (core)
[13:08] -queuebot:#ubuntu-release- Unapproved: python-oslo.privsep (yakkety-proposed/main) [1.13.0-0ubuntu1 => 1.13.0-0ubuntu1.1] (no packageset)
[14:09] <cyphermox> sru team: please reject os-prober from the xenial unapproved queue
[14:10] -queuebot:#ubuntu-release- Unapproved: s390-zfcp (xenial-proposed/main) [1.0.2ubuntu1 => 1.0.2ubuntu1.1] (no packageset)
[14:37] <rbasak> cyphermox: done
[14:37] <cyphermox> ta
[14:37] -queuebot:#ubuntu-release- Unapproved: accepted os-prober [source] (xenial-proposed) [1.70ubuntu3.1]
[14:40] -queuebot:#ubuntu-release- Unapproved: accepted partman-btrfs [source] (xenial-proposed) [18ubuntu1.1]
[14:42] -queuebot:#ubuntu-release- Unapproved: accepted virt-manager [source] (xenial-proposed) [1:1.3.2-3ubuntu1.16.04.3]
[14:46] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-57.78]
[15:24] <nacc> slangasek: thanks
[15:28] -queuebot:#ubuntu-release- Unapproved: icingaweb2 (xenial-proposed/universe) [2.1.0-1ubuntu1.1 => 2.1.0-1ubuntu1.2] (no packageset)
[15:40] <lamont> rbasak: https://pastebin.canonical.com/173584/ looks reasonable to me.  Poke me after you accept it into proposed, and I'll reroll my images and do the whole testing thing with all the other things
[15:44] <lamont> rbasak: assuming that we can override the 7-day agingb...
[15:44] <lamont> really really really need the SRU from last friday to land this friday
[15:44] <lamont> rbasak: smoser ^^
[15:53] <lamont> rbasak: for clarity, -1, UNLESS the decision is made to not delay the in-flight SRU for 1621615 from landing on schedule.
[15:59] -queuebot:#ubuntu-release- Unapproved: rejected resolvconf [source] (yakkety-proposed) [1.79ubuntu1.1]
[16:02] -queuebot:#ubuntu-release- Unapproved: resolvconf (yakkety-proposed/main) [1.79ubuntu1 => 1.79ubuntu1.1] (core)
[16:33] <mapreri> I wouldn't mind if somebody could look at that pbuilder SRU in yakkety-proposed :)
[16:34] <xnox> mapreri, does it replace pbuilder with an empty package that depends on sbuild? =)
[16:34] <mapreri> well... :)
[17:17] <jgrimm> rbasak, lamont, smoser: i'm going to rescind my request to update to cloud-init, let's get the current proposed all verified and into updates.
[17:20] -queuebot:#ubuntu-release- New binary: golang-github-geertjohan-go.rice [ppc64el] (zesty-proposed/universe) [0.0~git20160123.0.0f3f5fd-1] (no packageset)
[17:23] <rtg> can someone tell me why Zesty spl-linux and zfs-linux are still in proposed ? The brittny excuses don't make any sense to me.
[17:23] <infinity> rbasak: In theorym it would be good practice for us to QA all arch/flavour combos in a d-i build.  In practice, we've never really done so.
[17:24] <infinity> rbasak: Really, given the nature of d-i, that's something that could and should be automated, but whee.
[17:24] -queuebot:#ubuntu-release- New binary: pychromecast [amd64] (zesty-proposed/universe) [0.7.7-2] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: golang-github-geertjohan-go.rice [arm64] (zesty-proposed/universe) [0.0~git20160123.0.0f3f5fd-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: golang-github-geertjohan-go.rice [armhf] (zesty-proposed/universe) [0.0~git20160123.0.0f3f5fd-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-log-out-button [amd64] (zesty-proposed/universe) [1.0.6-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: python-dicttoxml [amd64] (zesty-proposed/universe) [1.7.4-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: heapdict [amd64] (zesty-proposed/universe) [1.0.0-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: pylama [amd64] (zesty-proposed/universe) [7.3.1-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: node-parse-filepath [amd64] (zesty-proposed/universe) [1.0.1-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: golang-github-geertjohan-go.rice [i386] (zesty-proposed/universe) [0.0~git20160123.0.0f3f5fd-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: locket [amd64] (zesty-proposed/universe) [0.2.0-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: python-django-etcd-settings [amd64] (zesty-proposed/universe) [0.1.11+dfsg-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: libamazon-s3-perl [amd64] (zesty-proposed/universe) [0.45-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: node-deprecated [amd64] (zesty-proposed/universe) [0.0.1-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: golang-github-geertjohan-go.rice [amd64] (zesty-proposed/universe) [0.0~git20160123.0.0f3f5fd-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: python-pyo [ppc64el] (zesty-proposed/universe) [0.8.1-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: python-pyo [amd64] (zesty-proposed/universe) [0.8.1-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: python-pyo [s390x] (zesty-proposed/universe) [0.8.1-1] (no packageset)
[17:29] <infinity> rtg: Looks like some tests went AWOL, and it's been spinlocked, waiting for results that are never coming back.
[17:29] <infinity> rtg: I'll retry 'em.
[17:30] <rtg> infinity, thanks, though I have to question why spl/zfs are being tested on i386. They really should only be installed on a 64 bit platform.
[17:31] <clivejo> infinity: is it possibly to upload a package but omit it for certain arch?
[17:32] <infinity> clivejo: Expand on the problem you're solving, not the solution you've chosen. :)
[17:32] -queuebot:#ubuntu-release- New binary: fis-gtm [amd64] (zesty-proposed/universe) [6.3-000A-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: fis-gtm [i386] (zesty-proposed/universe) [6.3-000A-1] (no packageset)
[17:32] <infinity> rtg: I suspect the test is actually a no-op.
[17:32] <clivejo> infinity: I'm trying to get krita 3.1.0 packaged and uploaded to archive
[17:32] <clivejo> its is failing on arm64 and armhf due to issues with opengl
[17:33] <infinity> clivejo: Given that krita isn't in the archive at all right now, that's a non-problem.
[17:33] -queuebot:#ubuntu-release- New binary: python-pyo [i386] (zesty-proposed/universe) [0.8.1-1] (no packageset)
[17:33] <infinity> (or the source package name is sometihng else?)
[17:33] <clivejo> https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-misc/+packages?field.name_filter=krita&field.status_filter=published&field.series_filter=zesty
[17:33] <clivejo> it was calligra
[17:34] <clivejo> I'm trying to get our seed updated
[17:34] <clivejo> but this issue with arm64 and armhf doesn't look fixable any time soon
[17:35] <infinity> It's likely the infamous GL versus GLES Qt thing.
[17:35] <infinity> Anyhow, no need to arch-restrict your package.
[17:35] <infinity> We can decide when it's in the archive what the best way forward is, delete the old binaries, or investigate the build failures, but arch-restricting won't actually help you with either of those things.
[17:36] <infinity> (ie: if you upload an arch-restricted package, it still won't migrate without intervention, and now we also don't have a build log to show us what's broken)
[17:37] <clivejo> I've asked cyphermox to run the magic script to allow me to upload, but don't think he's had a chance as yet
[17:37] <clivejo> but I'd like to get this uploaded ASAP
[17:37] -queuebot:#ubuntu-release- New binary: golang-github-geertjohan-go.rice [s390x] (zesty-proposed/universe) [0.0~git20160123.0.0f3f5fd-1] (no packageset)
[17:39] <infinity> Oh, hrm, this might be more subtle than just GL/GLES.
[17:39] <infinity> As in, it might also be fixable.
[17:39] <clivejo> infinity: :)
[17:40] -queuebot:#ubuntu-release- New binary: python-pyo [armhf] (zesty-proposed/universe) [0.8.1-1] (no packageset)
[17:40] <infinity> Well.  Okay.  It's GL/GLES, but not in the usual sense.
[17:40] -queuebot:#ubuntu-release- New binary: python-pyo [arm64] (zesty-proposed/universe) [0.8.1-1] (no packageset)
[17:41] <clivejo> infinity: I have to pop out for a bit, will you be around in a couple of hours?
[17:41] <infinity> It seems that many/most of those enums have long ago changes to modern names (ie: s/GL_HALF_FLOAT_ARB/GL_HALF_FLOAT/) and while GL supports backward compatibility for old code, GLES never has.
[17:41] <infinity> Anyhow.  I agree that expecting you to fix it might be a bit much.  Arch-restricting your package is also wrong.
[17:41] <infinity> So it's a conversation better had once it's uploaded.
[17:42] <clivejo> infinity: I can't upload it, "Error: The source package 'krita' does not exist in the Ubuntu primary archive in zesty, zesty-security, zesty-updates or zesty-proposed"
[17:42] <clivejo> Ill need a sponsor
[17:42] -queuebot:#ubuntu-release- New binary: golang-github-geertjohan-go.rice [powerpc] (zesty-proposed/universe) [0.0~git20160123.0.0f3f5fd-1] (no packageset)
[17:43] <infinity> clivejo: Oh, sure. But I'm not volunteering to sponsor it, I was answering your "can you arch-restrict it" question.
[17:44] <infinity> clivejo: To which the answer is: "yes, you can, but it won't do you any good or solve the problem you're trying to solve, and I'd prefer you don't".
[17:44] <clivejo> I get that
[17:57] -queuebot:#ubuntu-release- New binary: python-pyo [powerpc] (zesty-proposed/universe) [0.8.1-1] (no packageset)
[18:02] <lamont> jgrimm: ta
[18:24] -queuebot:#ubuntu-release- New binary: poppler [ppc64el] (zesty-proposed/main) [0.48.0-2ubuntu1] (desktop-core, ubuntu-server)
[18:25] -queuebot:#ubuntu-release- New binary: poppler [i386] (zesty-proposed/main) [0.48.0-2ubuntu1] (desktop-core, ubuntu-server)
[18:31] -queuebot:#ubuntu-release- New binary: poppler [armhf] (zesty-proposed/main) [0.48.0-2ubuntu1] (desktop-core, ubuntu-server)
[18:31] -queuebot:#ubuntu-release- New binary: poppler [powerpc] (zesty-proposed/main) [0.48.0-2ubuntu1] (desktop-core, ubuntu-server)
[18:34] -queuebot:#ubuntu-release- New binary: poppler [s390x] (zesty-proposed/main) [0.48.0-2ubuntu1] (desktop-core, ubuntu-server)
[18:38] -queuebot:#ubuntu-release- New binary: poppler [arm64] (zesty-proposed/main) [0.48.0-2ubuntu1] (desktop-core, ubuntu-server)
[18:40] -queuebot:#ubuntu-release- New binary: poppler [amd64] (zesty-proposed/main) [0.48.0-2ubuntu1] (desktop-core, ubuntu-server)
[19:26] <bdmurray> rbasak: What would you want to see as a test case for bug 1618900?  I haven't been able to recreate it and the change is "just" adding network.target and local-fs.target to the Before line of unattended-upgrades.service.
[19:26] <ubot5`> bug 1618900 in unattended-upgrades (Ubuntu Yakkety) "[Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"" [Medium,Triaged] https://launchpad.net/bugs/1618900
[19:29] <rbasak> bdmurray: IMHO, genuine difficult-to-reproduce race conditions and such can have a free pass. We can document that in the bug. We should check that the package still works though, especially for unattended-upgrades. So a separate test case - wait a few days, check that unattended-upgrades still still upgrading unattendedly.
[19:29] <rbasak> (free pass - provided the fix passes review, of course)
[19:30] <rbasak> bdmurray: which is a separate thing, actually. The focus seems to generally be that the bug being fixed is actually fixed, which is fine. IMHO, verification should also check that the standard use cases of the package aren't broken, which right now isn't explicitly stated in the process.
[19:31] <rbasak> Sometimes an SRU lands without any evidence that anyone checked that, which I think is wrong.
[19:31] <bdmurray> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification#How_to_perform_the_test
[19:32] <bdmurray> Use the software installed by the package in common ways
[19:32] <rbasak> That's not something anyone actually does though.
[19:33] <bdmurray> Your original statement was "explicitly stated", but I agree re it being done.
[19:33] <rbasak> At some point I intend to suggest adding a "[Test Plan]" section to the bug paperwork that details how this will be done. Then this could be checked before accepting from the queue, and the person marking v-d could confirm it was done which could be checked before releasing.
[19:34] <rbasak> explicitly> fair enough. It's explicitly in the process, but not in a part that anyone sees. Better? :)
[19:35] <bdmurray> rbasak: Given the pending SRU report and quantity of unverified things, I sort of feel like this is just gonna make things even slower.
[19:37] <rbasak> bdmurray: I'm not convinced we need to care about bugs that nobody is willing to drive. Anyone affected could check that the package still works and report that. If nobody can be bothered to do that, clearly the bug isn't important enough to anyone to fix.
[19:38] <rbasak> bdmurray: OTOH, if there is a process barrier such that people can't understand what they need to do, then I'm all for removing that.
[19:38]  * rbasak goes for dinner
[19:38] <bdmurray> Maybe we should review what's stuck.
[19:38] -queuebot:#ubuntu-release- Unapproved: apt (yakkety-proposed/main) [1.3.2ubuntu0.1 => 1.3.3] (core)
[19:48] <jbicha> we already have a [Test Case] section, don't we?
[19:58] -queuebot:#ubuntu-release- Unapproved: accepted apt [source] (yakkety-proposed) [1.3.3]
[20:02] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [amd64] (xenial-proposed/main) [4.8.0-32.34~16.04.1] (no packageset)
[20:02] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (yakkety-proposed/main) [4.8.0-32.34] (core, kernel)
[20:16] -queuebot:#ubuntu-release- New binary: coz-profiler [amd64] (zesty-proposed/universe) [0.0.git.20161130T1802-2ubuntu1] (no packageset)
[20:16] -queuebot:#ubuntu-release- New binary: coz-profiler [armhf] (zesty-proposed/universe) [0.0.git.20161130T1802-2ubuntu1] (no packageset)
[20:16] -queuebot:#ubuntu-release- New binary: coz-profiler [i386] (zesty-proposed/universe) [0.0.git.20161130T1802-2ubuntu1] (no packageset)
[20:17] -queuebot:#ubuntu-release- New binary: coz-profiler [powerpc] (zesty-proposed/universe) [0.0.git.20161130T1802-2ubuntu1] (no packageset)
[20:17] -queuebot:#ubuntu-release- New binary: coz-profiler [ppc64el] (zesty-proposed/universe) [0.0.git.20161130T1802-2ubuntu1] (no packageset)
[20:18] -queuebot:#ubuntu-release- New binary: coz-profiler [arm64] (zesty-proposed/universe) [0.0.git.20161130T1802-2ubuntu1] (no packageset)
[20:46] -queuebot:#ubuntu-release- New sync: zfcpdump-kernel (xenial-proposed/primary) [4.4-0ubuntu0.1]
[20:46] <xnox> slangasek, ^
[20:47] <xnox> slangasek, note this superseed the other NEW package with version 4.4-0ubuntu1~16.04.1
[20:49]  * slangasek nods
[20:51] -queuebot:#ubuntu-release- New: rejected zfcpdump-kernel [source] (xenial-proposed) [4.4-0ubuntu1~16.04.1]
[21:16] <infinity> xnox: How did they differ?
[21:31] <slangasek> infinity: one has corresponding GPL source, the other does not ;)
[21:37] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (yakkety-proposed/main) [0.92ubuntu1.1 => 0.92ubuntu1.2] (desktop-core, ubuntu-server)
[21:40] <xnox> infinity, the sync one has 120MB orig tarball, the previous one build-depended on linux-source or some such, which we don't currently guarantee to keep around.
[21:40] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (xenial-proposed/main) [0.90ubuntu0.2 => 0.90ubuntu0.3] (desktop-core, ubuntu-server)
[21:51] <infinity> xnox, slangasek: Ahh, fair enough.  We really should sort out some better built-using tracking in the LP domination code, etc.
[21:51] <infinity> But not today. :P
[21:56] <slangasek> xnox: debian/patches/debian-changes> hrm. expected?
[21:57] <infinity> 3.0-pretending-to-be-1.0?
[22:03] <slangasek> infinity: well, the new upload is 3.0 (quilt) where the previous was 3.0 (native).  I guess it's using the pristine 4.4 tarball, and all of the Ubuntu kernel delta winds up in debian/patches/debian-changes
[22:04] <infinity> slangasek: Right, the kernel itself is 1.0, which makes representing that in a 3.0 package curious.
[22:04] <infinity> xnox: Did you run the recontruct script before generating your patch?
[22:05] <infinity> xnox: It might not matter for this kernle anyway, since you touch a tiny subset of stuff, but because the kernel is 1.0, which can't represent deletions or symlinks, they have a script to fix it up to look like the git branch.
[22:05] <infinity> xnox: debian.master/reconstruct in the kernel source
[22:08] <slangasek> infinity: xnox just did the sync, he didn't prep this package
[22:20] <slangasek> infinity: so the question is if I should care about this enough to reject it
[22:35] <xnox> infinity, apw did the right thing.
[22:36] <xnox> infinity, and note that it is refactoring a basterdised version of a real kernel to make a zfcpdump-kernel.
[22:36] <xnox> with sources included.
[22:36] <xnox> it is not a "real flavour"
[22:36] <xnox> slangasek, to be honest, i think i should contribute patch to normal kernel builds to generate this zfcpdump kernel during normal s390x build.
[22:36] <xnox> because this is none-sence.
[22:39] <slangasek> xnox: I think the concern there was that it would either a) increase the QA burden for a kernel build that /shouldn't/ have any net changes with each upload, or b) result in us releasing not-QAed images
[22:39] <slangasek> (kernel images)
[22:40] <xnox> true. unless i automate the zfcpdump test.
[22:44] <infinity> To be fair, I think "generate it from the kernel build" was the solution both apw and I originally proposed.
[22:44] <infinity> And "we don't want to QA it" was the response. :P
[22:45] <xnox> at the end of the day, zfcdumping is for me to qa, due to restrictions in HMC which requires monkey to click things.
[22:46] <xnox> we did file requests to IBM to open up the APIs (the console does these things remotely so api is there, just not exposed over the automated transport)
[22:47] -queuebot:#ubuntu-release- New: accepted zfcpdump-kernel [sync] (xenial-proposed) [4.4-0ubuntu0.1]