=== maclin1 is now known as maclin [08:10] -queuebot:#ubuntu-release- New: rejected linux-aws [sync] (bionic-proposed) [4.4.0-1052.61] [08:10] -queuebot:#ubuntu-release- New: rejected linux-gke [sync] (bionic-proposed) [4.4.0-1034.34] [08:10] -queuebot:#ubuntu-release- New: rejected linux-kvm [sync] (bionic-proposed) [4.4.0-1019.24] [08:10] -queuebot:#ubuntu-release- New: rejected linux-meta-azure [sync] (bionic-proposed) [4.13.0.1011.12] [08:10] -queuebot:#ubuntu-release- New: rejected linux-azure [sync] (bionic-proposed) [4.13.0-1011.14] [08:10] -queuebot:#ubuntu-release- New: rejected linux-meta-aws [sync] (bionic-proposed) [4.4.0.1052.54] [08:10] -queuebot:#ubuntu-release- New: rejected linux-hwe [sync] (bionic-proposed) [4.13.0-36.40~16.04.1] [08:11] -queuebot:#ubuntu-release- New: rejected linux-meta-gke [sync] (bionic-proposed) [4.4.0.1034.35] [08:11] -queuebot:#ubuntu-release- New: rejected linux-meta-kvm [sync] (bionic-proposed) [4.4.0.1019.18] [08:11] -queuebot:#ubuntu-release- New: rejected linux-meta-hwe [sync] (bionic-proposed) [4.13.0.36.55] [08:20] jbicha, slangasek - is it just britney picking an arbitrary arch to blame things on. === maclin1 is now known as maclin [09:07] xnox: yeah, not sure what's going on, I can't figure out why the set of lxc packages won't migrate, gets blamed on different arch every time and I've done a number of local tests that show them all as co-installable, both within -proposed and when installing them on top of a system without -proposed (not depending on anything else that's in proposed) [09:12] stgraber, i smell, being stuck behind libunistring0 -> libunistring2 transition; let me add a transition tracker to verify that. [09:12] I didn't see it pull unistring2 when installing just the packages I care about from proposed [09:12] let me check that container [09:13] ii libunistring0:amd64 0.9.3-5.2ubuntu1 amd64 Unicode string library for C [09:13] that's the unistring in there after installing the entire lxc stack from proposed, so it's not pulling the new unistring in === maclin1 is now known as maclin [09:19] xnox, it needs a removal of freeipa IIRC, libunistring is all green [09:20] stgraber: I notice that you have a versioned breaks/replaces against lxc-common but that this package no longer exists in -proposed, so that should probably be unversioned Conflicts/Replaces and maybe Provides? [09:22] slangasek, can you please remove the ./vorlon:force-badtest tracker/all/s390x line? [09:23] thanks :) [09:23] LocutusOfBorg, yeah, i want to double check the tracker. ideally we should keep the trackers around, until things actually migrate. as sometimes people can regress migrations which are otherwise ready. [09:23] (and e.g. to see the packages to remove) [09:23] slangasek: oh, good catch. It was initially planned to transition it to a transitional package like some of the others but then just dropped as we don't have any rdepends on it other than our own packages [09:23] slangasek: I'll change that [09:23] xnox, I moved the tracker to finished once it became all green [09:23] feel free to add it back [09:24] stgraber: ok. I'm pretty sure it's not the cause of the migration failure, just something I noticed [09:24] * LocutusOfBorg might be wrong [09:24] LocutusOfBorg: tracker/all/s390x is marked 'flaky test'. Is the test no longer flaky? [09:25] slangasek, seems to pass now, but you can keep it there, it is not easy to test "flaky" :) [09:25] I saw it was failing for the same reason as other archs, and now with libunistring 0.9.9 it is green. === maclin1 is now known as maclin [09:25] I scheduled a second run and lets see [09:26] slangasek, question: curl and libunistring are entangled with kamailio... how can I build a kamailio version with older curl to see everything migrate, and then no change rebuild it again? this would make things easier [09:26] maybe a kamailio with curl taken from release? is it possible? [09:26] LocutusOfBorg, well, we need curl migration too.... [09:26] and ruby-defaults mirgration.... [09:26] LocutusOfBorg: curl is really blocked by xmltooling. All the rest is just about ready to go on both sides of that transition. Please don't try to play build env tricks to circumvent [09:27] xmltooling and net-cpp and AFAIK that's the complete list [09:27] ack but curl is also r-base entangled [09:31] -queuebot:#ubuntu-release- Unapproved: grub2 (artful-proposed/main) [2.02~beta3-4ubuntu7.2 => 2.02~beta3-4ubuntu7.3] (core) [09:32] -queuebot:#ubuntu-release- Unapproved: grub2-signed (artful-proposed/main) [1.85.2 => 1.85.3] (core) [09:32] scilab ftbfs on i386 <-- this is a curl blocker [09:52] -queuebot:#ubuntu-release- Unapproved: rejected virtualbox [source] (artful-proposed) [5.1.34-dfsg-0ubuntu1.17.10.1~17.10.1] [10:10] who is trying to rebuild xmltooling? :P [10:11] me, only once, sorry! [10:11] ;) [10:11] I was trying to sort out where the issue was, and I found it, with the debian rc bug too [10:11] it definitely isn't going to fix itself [10:11] meh, "upstream going to do the work, not sure when" [10:11] yes, indeed, but apt could be more verbose when indirect dependencies are conflicting [10:13] LocutusOfBorg: conflict between libxml-security-dev and libssl-dev which is not straightforwardly resolvable [11:21] slangasek, there is no need to tweak the debian packaging, to make kamailio build against curl in release, just build in a ppa with "release only repo enabled" and copy binaries to the archive (I'm trying to understand, I don't want to do it, unless you ask me) [11:26] slangasek: not terribly high priority, but on friday we talked about allowing cloud-init into xenial. and delayed primarily because of 'friday'. [11:26] being it is now monday, could you re-evaluate ? [11:31] -queuebot:#ubuntu-release- Unapproved: accepted aptdaemon [source] (artful-proposed) [1.1.1+bzr982-0ubuntu17.1] [12:12] -queuebot:#ubuntu-release- Unapproved: accepted isc-dhcp [source] (artful-proposed) [4.3.5-3ubuntu2.3] [12:16] -queuebot:#ubuntu-release- Unapproved: accepted isc-dhcp [source] (xenial-proposed) [4.3.3-5ubuntu12.10] [12:16] -queuebot:#ubuntu-release- Unapproved: accepted isc-dhcp [source] (trusty-proposed) [4.2.4-7ubuntu12.13] [12:19] flocculant: Just double checking, y'all aren't doing Beta 1 right? [12:25] -queuebot:#ubuntu-release- Unapproved: accepted nplan [source] (artful-proposed) [0.32~17.10.3] [12:26] smoser: from my side, the delay was because "it's not a regression in xenial so no reason for extraordinary processing" :) let me have a quick look [12:28] fair [12:30] slangasek: updated my lxc hint so we'll see if we get any luckier with this upload... if it doesn't migrate, I really have no clue what's going on, the output doesn't make much sense to me [12:32] smoser: the latest version has only aged 2 days in xenial-proposed, but that's of course because of the additional upload to fix the regression. I'm indifferent to whether we release it now, if you are happy that these are ready to release then I can do so [12:32] blackboxsw: ^ [12:32] i think we're good. [12:33] +1 slangasek yes I also validated that same set of changes on artful-updates which worked well [12:38] -queuebot:#ubuntu-release- Unapproved: rejected virtualbox-hwe [source] (xenial-proposed) [5.1.34-dfsg-0ubuntu1.16.04.1~16.04.1] [12:38] -queuebot:#ubuntu-release- Unapproved: rejected virtualbox [source] (xenial-proposed) [5.1.34-dfsg-0ubuntu1.16.04.1~16.04.1] [12:43] -queuebot:#ubuntu-release- Unapproved: rejected nplan [source] (xenial-proposed) [0.32~16.04.4] [12:58] slangasek: right, so we're back to the whole lxc stack being considered valid candidates but nothing moving... [13:10] cyphermox: I'm accepting it, but please add SRU info to LP: #1747714 o/ [13:10] Launchpad bug 1747714 in nplan (Ubuntu Xenial) "network manager snap service name regression" [High,In progress] https://launchpad.net/bugs/1747714 [13:11] -queuebot:#ubuntu-release- Unapproved: accepted nplan [source] (xenial-proposed) [0.32~16.04.4] [13:15] stgraber: I think it needs hinting with python3-lxc [13:15] sec [13:16] I thought I skiptested all the relevant bits [13:16] otherwise britney wouldn't consider them all valid candidates right? [13:17] stgraber: they need to migrate in the same transaction and britney isn't considering python3-lxd with the rest [13:17] it's only doing Trying easy from autohinter: golang-gopkg-lxc-go-lxc.v2/0.0~git20180119.b964baa-1ubuntu3 lxc/3.0.0~beta1-0ubuntu3 lxc-templates/3.0.0~beta1-0ubuntu1 [13:17] odd [13:18] britney> easy golang-gopkg-lxc-go-lxc.v2/0.0~git20180119.b964baa-1ubuntu3 lxc/3.0.0~beta1-0ubuntu3 lxc-templates/3.0.0~beta1-0ubuntu1 python3-lxc/3.0.0~beta1-0ubuntu2 [13:18] Trying easy from hint-tester: golang-gopkg-lxc-go-lxc.v2/0.0~git20180119.b964baa-1ubuntu3 lxc/3.0.0~beta1-0ubuntu3 lxc-templates/3.0.0~beta1-0ubuntu1 python3-lxc/3.0.0~beta1-0ubuntu2 [13:18] ... [13:18] SUCCESS (379/0) [13:18] I'll add that for the next run [13:42] yay, thanks [13:44] Laney: hey, is your "+1" an approval for the LP: #1752928 FFe? Should the bug be set to Triaged? [13:44] Launchpad bug 1752928 in ubuntu-meta (Ubuntu) "[FFe] GNOME 3.28" [Undecided,New] https://launchpad.net/bugs/1752928 [13:50] sil2100: yeah, I probably forgot, please feel free to do it === juliank_ is now known as juliank === blackboxsw_ is now known as blackboxsw === tgm4883_ is now known as tgm4883 [14:59] -queuebot:#ubuntu-release- Unapproved: zfs-linux (artful-proposed/main) [0.6.5.11-1ubuntu3.1 => 0.6.5.11-1ubuntu3.2] (core) [15:19] -queuebot:#ubuntu-release- New sync: linux-aws (bionic-proposed/primary) [4.15.0-1001.1] [15:25] -queuebot:#ubuntu-release- New: accepted linux-aws [sync] (bionic-proposed) [4.15.0-1001.1] [15:26] -queuebot:#ubuntu-release- New sync: linux-meta-aws (bionic-proposed/primary) [4.15.0.1001.1] [15:27] -queuebot:#ubuntu-release- New sync: linux-azure (bionic-proposed/primary) [4.15.0-1002.2] [15:28] -queuebot:#ubuntu-release- New: accepted linux-azure [sync] (bionic-proposed) [4.15.0-1002.2] [15:28] -queuebot:#ubuntu-release- New: accepted linux-meta-aws [sync] (bionic-proposed) [4.15.0.1001.1] [15:31] -queuebot:#ubuntu-release- New binary: linux-meta-aws [amd64] (bionic-proposed/none) [4.15.0.1001.1] (kernel) [15:31] -queuebot:#ubuntu-release- New binary: linux-meta-azure [amd64] (bionic-proposed/none) [4.15.0.1002.3] (kernel) [15:33] -queuebot:#ubuntu-release- New binary: linux-meta-gcp [amd64] (bionic-proposed/none) [4.15.0.1001.2] (kernel) [15:39] -queuebot:#ubuntu-release- New: accepted linux-meta-aws [amd64] (bionic-proposed) [4.15.0.1001.1] [15:44] -queuebot:#ubuntu-release- New: accepted linux-meta-azure [amd64] (bionic-proposed) [4.15.0.1002.3] [15:48] -queuebot:#ubuntu-release- New: accepted linux-meta-gcp [amd64] (bionic-proposed) [4.15.0.1001.2] [16:31] -queuebot:#ubuntu-release- New binary: linux-azure [amd64] (bionic-proposed/main) [4.15.0-1002.2] (kernel) [16:38] -queuebot:#ubuntu-release- New sync: hg-git (bionic-proposed/primary) [0.8.11-1] [16:44] -queuebot:#ubuntu-release- New sync: libauth-googleauth-perl (bionic-proposed/primary) [1.02-1] [16:45] -queuebot:#ubuntu-release- New sync: libwww-shorten-5gp-perl (bionic-proposed/primary) [1.030-1] [16:48] -queuebot:#ubuntu-release- New binary: linux-aws [amd64] (bionic-proposed/main) [4.15.0-1001.1] (kernel) [17:35] tsimonq2: yes we are [17:36] tsimonq2: it's only alpha's we see no gain [17:37] flocculant: Since when do y'all do Beta 1? [17:37] XD [17:39] since as long as I've been around and longer - it's alpha's we don't do [17:39] though I think a while back we had an issue at b1 time and I was refusing to release it in that state [17:40] I'd argue for beta's it's alpha's my position is clear on :D [17:41] :D [17:41] OK [17:48] -queuebot:#ubuntu-release- New binary: linux-gcp [amd64] (bionic-proposed/main) [4.15.0-1001.1] (kernel) [20:53] -queuebot:#ubuntu-release- Unapproved: python-cryptography (artful-proposed/main) [1.9-1 => 1.9-1ubuntu1] (core) [20:58] -queuebot:#ubuntu-release- Unapproved: python-cryptography (xenial-proposed/main) [1.2.3-1ubuntu0.1 => 1.2.3-1ubuntu0.2] (ubuntu-desktop, ubuntu-server) === DalekSec_ is now known as DalekSec