[07:08] <tjaalton> bdmurray: oops, sorry for missing the xserver-lts-xenial diff, I'll merge it now and upload again
[07:16] <tjaalton> but not before the sru is released of course
[11:13] <xnox> can gnupg2 triggered libmail-gnupg-perl test use (libmail-gnupg-perl,gnupg) from proposed?
[11:14] <xnox> similar with apt
[11:14] <xnox> or like hint apt/gnupg2/libmail-gnupg-perl to go in together
[11:17] <doko> ginggs_: do you want to look at the shogun ftbfs, or should we just demote it?
[11:20] <ginggs_> doko: please demote it, that looks like debian #835411
[12:49] <xnox> Laney, is there some way to hint gnupg2 to go in together with libmail-gnupg-perl.
[12:50] <Laney> hi xnox
[12:50] <xnox> apt tests actually passed and it migrated, libmail-gnupg-perl in proposed also passes its tests, and snapd is all good as well.
[12:50] <Laney> sure, but that's not much use if the tests are failing
[12:51] <Laney> you probably want them re-run?
[12:51] <xnox> yes but libmail-gnupg-perl & gnupg2 should be rerun with proposed.
[12:52] <xnox> and the retry button doesn't offer me to do that.
[12:53] <Laney> ok
[12:53] <Laney> 'go in together' means something else to me
[12:53] <xnox> as in testing libmail-gnupg-perl from release with gnugp2 from proposed will always fail.
[12:54] <xnox> libmail-gnupg-perl from release works with gnupg2 in release; libmail-gnupg-perl from proposed works with gnupg2 in proposed or release;
[12:55] <jbicha> xnox: you can manually append &trigger=gnupg2/2.1.15-1ubuntu2 to the url the retry button suggests
[12:56] <xnox> that bit is right.
[12:57] <xnox> i think i need two triggers.... gnupg2 and libgnupg-interface-perl/$proposed-version
[13:01] <Laney> xnox: I did them for you
[13:01] <xnox> thanks
[13:02] <xnox> is there a magic how-to? granted i don't cause such things often.....
[13:02] <Laney> Maybe you can pass &trigger= more than once
[13:02] <Laney> I just ran a command on snakefruit
[13:06] <xnox> i wonder if my depends are not explicit enough in the libmail-gnupg-perl case
[16:05] <xnox> Laney, can gnupg2 be hinted with skiptests and hinted to libgnupg-interface-perl to migrate together with gnupg2?
[16:07] <xnox> horum looking at http://autopkgtest.ubuntu.com/packages/libm/libmail-gnupg-perl/yakkety/amd64 triggers are still incorrect
[16:07]  * xnox fiddles
[16:08] <xnox> tadah https://autopkgtest.ubuntu.com/request.cgi?release=yakkety&arch=amd64&package=libmail-gnupg-perl&trigger=gnupg2%2F2.1.15-1ubuntu2&trigger=libmail-gnupg-perl%2F0.22-1ubuntu2
[16:34] <Laney> xnox: did that work?
[16:34] <Laney> I'm not that comfortable forcing gpg-related tests
[17:42] <doko> kenvandine: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-007/+sourcepub/6843960/+listing-archive-extra   there is no need to drop the java package and the java build-deps
[17:42] <kenvandine> doko, why?  we don't want to do an MIR for tomcat
[17:42] <doko> kenvandine: we did the archive reorg last cycle
[17:43] <doko> kenvandine: build-deps from universe are fine
[17:44] <kenvandine> oh they are?
[17:44] <kenvandine> that's good :)
[17:44] <teward> unless they add new runtime deps
[17:44] <kenvandine> ok
[17:44] <kenvandine> they don't in this case
[17:44] <teward> s/new runtime deps/new runtime binary dependencies on something in universe as a result of building with the Universe package(s)/
[17:44]  * teward was imprecise
[17:45] <doko> and I assume the java module will end up in universe anyway