=== cpaelzer_afk is now known as cpaelzer_ === rbasak_ is now known as rbasak === cpaelzer is now known as cpaelzer_afk === cpaelzer_afk is now known as cpaelzer === FourDollars_ is now known as FourDollars === rvba` is now known as rvba === cpaelzer is now known as cpaelzer_afk === didrocks1 is now known as didrocks === cpaelzer_afk is now known as cpaelzer [13:54] vivid is EOL, so can all the remaining uploads on SRU queue be rejected? === cpaelzer is now known as cpaelzer_afk [14:16] tjaalton, it isnt EOL for phone and snappy ... perhaps people want to chrry pick stuf from proposed to their build PPAs first [14:18] ok, I won't touch it === cpaelzer_afk is now known as cpaelzer === ant_ is now known as Guest60739 === sil2100_ is now known as sil2100 === cjwatson_ is now known as cjwatson [16:49] * flexiondotorg_ tickles infinity to inquire about Xubuntu Base and Ubuntu MATE Base. === chrisccoulson_ is now known as chrisccoulson === narindergupta is now known as narindergupta_aw === doko_ is now known as doko [18:56] utlemming: hi, still working on the raspi2 images and I have some questions about intent of some of the binary hooks that I'm hoping you can shed light on [18:57] utlemming: specifically, 030-root-tarball.binary - this is doing kernel and bootloader removal... this is because it's creating a separate root tarball artifact, I guess? [18:59] well, I guess I've answered that particular question by reading on in the code [18:59] but now I need to see what we should do here... AFAICS when building for a subarch we should simply never build the rootfs bits [19:07] slangasek, rootfs.tar.gz has kernel/bootloader bits removed, and the result becomes lxc image and lxd image (after a metadata tarball is built elsewhere) [19:08] * slangasek nods [19:08] slangasek, the generated /boot/grub from ec2 emul remains inside it. [19:08] grub ec2 emul thing [19:08] so for a subarch build, we should just skip the rootfs generation [19:11] * slangasek wonders why cloud image livefs builds only list the manifests as artifacts [19:24] slangasek, i wonder why SHA512SUMS file is not generated. [19:27] xnox: maybe it is, but is hidden somewhere? [19:27] slangasek, =)))))))) youd't think that, right. [19:28] but quite specifically, the actual images are not shown as output artifacts [19:37] slangasek, btw they have to be collected pretty fast, as launchpad agreesively expires / deletes them. [19:37] slangasek, this is why cpc builds in jenkins, poll, download and store artifacts in swift. [19:37] erm ok [19:38] slangasek, oh the irony, if the same swift is used by both. [19:38] pretty sure it is :) [19:39] slangasek, please RM unity-scope-snappy, defunct, unusable, ftbfs (multiple reasons), not supported upstream, change of api & directly. [19:39] https://bugs.launchpad.net/ubuntu/+source/unity-scope-snappy/+bug/1542451 [19:39] Launchpad bug 1542451 in unity-scope-snappy (Ubuntu) "RM: unity-scope-snappy" [Critical,Triaged] [19:39] slangasek, canonical upstream approved removal. [19:39] not seeded. [19:39] and it has invalid Built-Using tags =) [19:42] xnox: Task: ubuntu-desktop-next ? [19:43] slangasek, i wonder where you get that idea from [19:43] from the Packages file [19:43] which is not authoritative, is it? [19:44] xnox: it's not the source, it is authoritative. Are you cheekily suggesting to me that you've already removed it from the seed? [19:44] slangasek, no, i'm suggesting that desktop team has dropped "ubuntu-desktop-next" a few cycles back. [19:44] um [19:45] sounds like they didn't communicate that to the archive admins, then :) [19:45] Laney, is ubuntu-desktop-next a thing? [19:45] slangasek, if I were an AA... [19:48] ya ba dibba dibba dibba dibba dibba dibba dum? [19:48] slangasek, well, meta pacakge did disappear. so an AA was involved. [19:48] $ rmadison ubuntu-desktop-next [19:48] ubuntu-desktop-next | 1.221 | vivid/universe | amd64, armhf, i386 [19:48] .. [19:49] one time, and one time only, vivid special. [19:49] removing the metapackage might well be independent of removing the task [19:49] https://launchpad.net/ubuntu/+source/ubuntu-touch-meta/1.250 [19:49] and the task still exists in ubuntu-touch.xenial [19:50] so, lp:~ubuntu-core-dev/ubuntu-seeds/ubuntu-touch.xenial please [19:50] ¯\_(ツ)_/¯ [19:51] done [19:53] hmm ok [19:53] well, I assigned the bug to the desktop team, so we can still grab their review to confirm before removing the package [21:13] when is featurefreeze again? [21:14] In two weeks. [21:14] thanks. i would check but the wiki and my tablet here aren't behaving :/