=== 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 | ||
tjaalton | vivid is EOL, so can all the remaining uploads on SRU queue be rejected? | 13:54 |
---|---|---|
=== cpaelzer is now known as cpaelzer_afk | ||
ogra_ | tjaalton, it isnt EOL for phone and snappy ... perhaps people want to chrry pick stuf from proposed to their build PPAs first | 14:16 |
tjaalton | ok, I won't touch it | 14:18 |
=== 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 | ||
* flexiondotorg_ tickles infinity to inquire about Xubuntu Base and Ubuntu MATE Base. | 16:49 | |
=== chrisccoulson_ is now known as chrisccoulson | ||
=== narindergupta is now known as narindergupta_aw | ||
=== doko_ is now known as doko | ||
slangasek | 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:56 |
slangasek | 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:57 |
slangasek | well, I guess I've answered that particular question by reading on in the code | 18:59 |
slangasek | 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 | 18:59 |
xnox | 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:07 |
* slangasek nods | 19:08 | |
xnox | slangasek, the generated /boot/grub from ec2 emul remains inside it. | 19:08 |
xnox | grub ec2 emul thing | 19:08 |
slangasek | so for a subarch build, we should just skip the rootfs generation | 19:08 |
* slangasek wonders why cloud image livefs builds only list the manifests as artifacts | 19:11 | |
xnox | slangasek, i wonder why SHA512SUMS file is not generated. | 19:24 |
slangasek | xnox: maybe it is, but is hidden somewhere? | 19:27 |
xnox | slangasek, =)))))))) youd't think that, right. | 19:27 |
slangasek | but quite specifically, the actual images are not shown as output artifacts | 19:28 |
xnox | slangasek, btw they have to be collected pretty fast, as launchpad agreesively expires / deletes them. | 19:37 |
xnox | slangasek, this is why cpc builds in jenkins, poll, download and store artifacts in swift. | 19:37 |
slangasek | erm ok | 19:37 |
xnox | slangasek, oh the irony, if the same swift is used by both. | 19:38 |
slangasek | pretty sure it is :) | 19:38 |
xnox | slangasek, please RM unity-scope-snappy, defunct, unusable, ftbfs (multiple reasons), not supported upstream, change of api & directly. | 19:39 |
xnox | https://bugs.launchpad.net/ubuntu/+source/unity-scope-snappy/+bug/1542451 | 19:39 |
ubot5` | Launchpad bug 1542451 in unity-scope-snappy (Ubuntu) "RM: unity-scope-snappy" [Critical,Triaged] | 19:39 |
xnox | slangasek, canonical upstream approved removal. | 19:39 |
xnox | not seeded. | 19:39 |
xnox | and it has invalid Built-Using tags =) | 19:39 |
slangasek | xnox: Task: ubuntu-desktop-next ? | 19:42 |
xnox | slangasek, i wonder where you get that idea from | 19:43 |
slangasek | from the Packages file | 19:43 |
xnox | which is not authoritative, is it? | 19:43 |
slangasek | 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 |
xnox | slangasek, no, i'm suggesting that desktop team has dropped "ubuntu-desktop-next" a few cycles back. | 19:44 |
slangasek | um | 19:44 |
slangasek | sounds like they didn't communicate that to the archive admins, then :) | 19:45 |
xnox | Laney, is ubuntu-desktop-next a thing? | 19:45 |
xnox | slangasek, if I were an AA... | 19:45 |
slangasek | ya ba dibba dibba dibba dibba dibba dibba dum? | 19:48 |
xnox | slangasek, well, meta pacakge did disappear. so an AA was involved. | 19:48 |
xnox | $ rmadison ubuntu-desktop-next | 19:48 |
xnox | ubuntu-desktop-next | 1.221 | vivid/universe | amd64, armhf, i386 | 19:48 |
xnox | .. | 19:48 |
xnox | one time, and one time only, vivid special. | 19:49 |
slangasek | removing the metapackage might well be independent of removing the task | 19:49 |
xnox | https://launchpad.net/ubuntu/+source/ubuntu-touch-meta/1.250 | 19:49 |
slangasek | and the task still exists in ubuntu-touch.xenial | 19:49 |
slangasek | so, lp:~ubuntu-core-dev/ubuntu-seeds/ubuntu-touch.xenial please | 19:50 |
xnox | ¯\_(ツ)_/¯ | 19:50 |
xnox | done | 19:51 |
slangasek | hmm ok | 19:53 |
slangasek | well, I assigned the bug to the desktop team, so we can still grab their review to confirm before removing the package | 19:53 |
teward | when is featurefreeze again? | 21:13 |
infinity | In two weeks. | 21:14 |
teward | thanks. i would check but the wiki and my tablet here aren't behaving :/ | 21:14 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!