[00:00]  * cyphermox has cinderella syndrome and logs off.
[00:00] <slangasek> fossfreedom: hi, so the livecd-rootfs change has landed to install snaps from marked channels, for future-proofing, as per https://wiki.ubuntu.com/UbuntuSeededSnaps; you'll need to open the stable/ubuntu-18.04 branch for ubuntu-budgie-welcome (after which you can close it again)
[00:01] <infinity> budgie-welcome?
[00:01] <infinity> Does it come with all the same fun that mate-welcome does?
[00:01] <slangasek> unknown to me
[00:01] <slangasek> but it currently causes a build failure
[00:05] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Bionic Beta 1] (20180306.1) has been added
[00:06] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Bionic Beta 1] (20180306.1) has been added
[00:06] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Bionic Beta 1] (20180306.1) has been added
[00:06] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Bionic Beta 1] (20180306.1) has been added
[00:07] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Bionic Beta 1] (20180306) has been added
[00:07] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Bionic Beta 1] (20180306) has been added
[00:08] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Bionic Beta 1] (20180306.1) has been added
[00:08] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Bionic Beta 1] (20180306.1) has been added
[00:13] <mwhudson> slangasek: would it be productive for me to stare at update_output.txt re: those packages you were complaining about?
[00:18] <slangasek> mwhudson: I got it sorted, adding cmake to the hint made everything happy
[00:18] <mwhudson> slangasek: woot
[00:18] <slangasek> I believe it will all migrate in the next run
[00:18] <tsimonq2> \o\ /o/ \o\ /o/
[00:18] <slangasek> which I only worked out via lp:~laney/ubuntu-archive-tools/update-output-helper
[00:19] <slangasek> the beta1 freeze also blocks the libunistring freeze now, though.  do lubuntu want that unblocked?
[00:20]  * mwhudson runs watch -n 60 -g 'curl --silent http://archive.ubuntu.com/ubuntu/dists/bionic-proposed/{main,universe,restricted,multiverse}/source/Sources.gz | zcat | grep-dctrl -sPackage . | wc -l'
[00:20] <wxl> tbh i doubt we care too much slangasek :)
[00:21]  * tsimonq2 thinks that lp:ubuntu-archive-tools should be converted to Git. :P
[00:22] <slangasek> wxl: considering this is a library transition that actually affects /your/ packages, I would be looking for an affirmative indication that you want it accepted before beta, rather than just "don't care"
[00:23] <wxl> slangasek: put differently, i think lubuntu would be fine either way, but feel free to unblock it.
[00:40] <bashfulrobot> slangasek: hi there, I might be able to help out with your question to fossfreedom.
[00:41] <slangasek> bashfulrobot: if you have collaborator rights on the snap
[00:46] <bashfulrobot> I'm the one who published it originally. I have access to that account. I'm also the one who has interacted with the form to get the classic confinement and everything done. <---- slangasek
[00:47] <slangasek> k then :)
[00:48] <slangasek> bashfulrobot: then please open the 'ubuntu-18.04' branch, then close it again
[00:49] <slangasek> bashfulrobot: once that's done, someone can kick off another candidate build for beat1
[00:49] <slangasek> beta1
[01:10] <bashfulrobot> slangasek: are you talking about within the snap dashboard? Or another location?
[01:20] <mwhudson> what's with all the failing ruby autopkgtests
[01:22] <tsimonq2> s/ruby/node/
[01:23] <mwhudson> and not or
[01:25] <tsimonq2> heh right
[01:27] -queuebot:#ubuntu-release- New source: ukwm (bionic-proposed/primary) [1.1.7-0ubuntu1]
[01:30] <tsimonq2> handsome_feng: ^^^^
[01:32] <handsome_feng> tsimonq2: Thanks!
[01:32] <tsimonq2> handsome_feng: np!
[01:52] -queuebot:#ubuntu-release- New source: peony-extensions (bionic-proposed/primary) [1.1.1-0ubuntu1]
[01:55] <infinity> mwhudson: Do they take the form of ruby (perhaps just 2.3) whining about not being able to load external bits?
[01:55] <infinity> mwhudson: If so, I ran into that earlier, and it warrants looking at, I think (or dropping ruby2.3, if that was planned for bionic)
[01:55] <mwhudson> infinity: yes, seems so
[01:59] <infinity> mwhudson: I suppose it's plausible that ruby's custom dlopen-like loader is broken with glibc 2.7, but because we only trigger direct rdeps, not rdeps of rdeps, we didn't get coverage on that.
[01:59] <infinity> mwhudson: Anything that grubs around at the ELF level trying to be tricky is skating on thin ice.
[01:59] <infinity> *cough*ffi*cough*
[01:59] <mwhudson> haha
[02:00] <infinity> s/2.7/2.27/
[02:00] <infinity> That missing 2 made that a very confusing statement.
[02:29] -queuebot:#ubuntu-release- New source: kylin-video (bionic-proposed/primary) [1.1.5-0ubuntu1]
[03:39] <mwhudson> heh heh http://autopkgtest.ubuntu.com/packages/g/golang-github-hashicorp-atlas-go/bionic/amd64
[05:45] -queuebot:#ubuntu-release- Unapproved: proftpd-dfsg (xenial-proposed/universe) [1.3.5a-1build1 => 1.3.5a-1.1] (no packageset)
[05:47] <tsimonq2> That sponsoree for proftpd-dfsg has been waiting three months for someone to upload that, so it'd be good if someone could process that fairly soon.
[06:00] <flocculant> infinity tsimonq2 - interesting discussion re milestones
[06:01] <infinity> tsimonq2: Was that a sync from Debian?
[06:02] <infinity> tsimonq2: If not, you misspelled '1ubuntu1'
[06:03] <tsimonq2> infinity: sigh, indeed I did.
[06:04] <tsimonq2> infinity: There, reject the oldest one in the queue, I uploaded one with the right version number.
[06:05] -queuebot:#ubuntu-release- Unapproved: proftpd-dfsg (xenial-proposed/universe) [1.3.5a-1build1 => 1.3.5a-1ubuntu0.1] (no packageset)
[06:05] <tsimonq2> infinity: ^^^ better, right?
[06:06] <tsimonq2> flocculant: I'll probably go over the notes this weekend and draft a proposal or something.
[06:07] <flocculant> tsimonq2: works for me - I know I often tell you my position, but it does come from thought, not just to make you lol a bit ;)
[06:07]  * flocculant particularly likes not publishing them
[06:07] <tsimonq2> flocculant: heh :)
[06:12] <slangasek> bashfulrobot: yes, it can be done through the snap dashboard.  Maybe it can also be done through the snapcraft CLI, but I'm not sure what the command would be there
[06:14] <slangasek> mwhudson, infinity: get ruby-defaults to migrate, so ruby in bionic release actually points to ruby2.5; then retest with ruby2.5; then tell the ruby maintainers to fix their interpreter package so that transitions are managed correctly like python, instead of leaving us with a set of packages which is installable but inconsistent.
[06:16] <slangasek> flexiondotorg: hi, same thing for ubuntu-mate as for ubuntu-budgie above: pulsemixer needs an ubuntu-18.04 branch opened in the snap store so that the liveCD can install it in a way that's conformant with the seeded snap policy
[06:18] <mwhudson> slangasek: ahah
[06:18] <mwhudson> step 1 looks like heaps of fun
[06:19] <flexiondotorg> slangasek: Do you mean a track?
[06:20] <slangasek> flexiondotorg: no, a branch
[06:21] <flexiondotorg> What ia the purpose of the branch?
[06:21] <slangasek> flexiondotorg: https://wiki.ubuntu.com/UbuntuSeededSnaps#Channel_availability
[06:21]  * flexiondotorg reads... 
[06:22] <slangasek> flexiondotorg: it needs to be opened once and then you can close it; but if it's never been opened, the snap client can't pin the branch, so there is no escape hatch if in the future you need to diverge from the 'stable' channel
[06:47] <bashfulrobot> slangasek: thanks for the clarification. I just wasn't sure if you were referencing that or else where, say LP.
[07:07] <xnox> jamespage, pinging slangasek to review percona stuff....
[07:21] <bashfulrobot> slangasek: I must be missing something. I don't see anywhere to create a branch in the snap dashboard. Still looking. Or I'm bind.
[07:35] <flexiondotorg> slangasek: pulsemixer branch for ubuntu-18.04 has been opened and closed.
[07:35] <flexiondotorg> bashfulrobot: You need to use snapcraft.
[07:36] <flexiondotorg> `snapcraft release --help`
[07:38] <acheronuk> when is the deadline for deciding to include snaps or not?
[07:44] <slangasek> flexiondotorg: thanks, retrying the ubuntu-mate build
[07:47] <flexiondotorg> slangasek: I assume I'll need to do the same for other seeded snap on Ubuntu MATE.
[07:48] <slangasek> flexiondotorg: heh, yes
[07:48] <flexiondotorg> doing it now....
[07:48] <slangasek> flexiondotorg: sorry, I hadn't checked the seeds
[07:53] <flexiondotorg> slangasek: All done.
[07:56] <flexiondotorg> slangasek: Here comes some build logs for the armhf build failues we discussed yesterday.
[07:56] <flexiondotorg> https://launchpadlibrarian.net/359270302/buildlog_snap_ubuntu_xenial_armhf_software-boutique_BUILDING.txt.gz
[07:56] <slangasek> wgrant: ^^
[07:56] <slangasek> :)
[07:57] <flexiondotorg> https://launchpadlibrarian.net/359118374/buildlog_snap_ubuntu_xenial_armhf_software-boutique_BUILDING.txt.gz
[07:58] <flexiondotorg> https://launchpadlibrarian.net/359270343/buildlog_snap_ubuntu_xenial_armhf_ubuntu-mate-welcome_BUILDING.txt.gz
[07:58] <flexiondotorg> https://launchpadlibrarian.net/359118572/buildlog_snap_ubuntu_xenial_armhf_ubuntu-mate-welcome_BUILDING.txt.gz
[07:59] <flexiondotorg> slangasek wgrant Those failures were alongside successful builds on amd64, arm64 and i386.
[07:59] <bashfulrobot> flexiondotorg: thanks for the clarification!!
[07:59] <flexiondotorg> bashfulrobot: yw :-)
[08:06] <wgrant> slangasek, flexiondotorg: Isn't that just the snapcraft !x86 SRU regression?
[08:06] <wgrant> https://github.com/snapcore/snapcraft/commit/84aaac591a0a3578d91e2a0e25bfb9ce8e546a83
[08:21] <bashfulrobot> slangasek: I released to stable/ubuntu-18.04 for 32/64bit
[08:22] <bashfulrobot> So we should be good to trigger the build
[08:23] <bashfulrobot> I'll leave the branch for now until we know the seeds work, then I'll remove it later.
[08:24] <bashfulrobot> https://www.irccloud.com/pastebin/Sa5T5Vxt
[08:25] <bashfulrobot> I'm heading off to bed, but will check in tomorrow slangasek . Thanks for the heads up.
[08:25]  * bashfulrobot passing out
[08:26] -queuebot:#ubuntu-release- Unapproved: google-cloud-sdk (trusty-proposed/partner) [191.0.0-0ubuntu1~14.04.0 => 191.0.0-0ubuntu2~14.04.0] (no packageset)
[08:26] -queuebot:#ubuntu-release- Unapproved: google-cloud-sdk (xenial-proposed/partner) [191.0.0-0ubuntu1~16.04.0 => 191.0.0-0ubuntu2~16.04.0] (no packageset)
[08:26] -queuebot:#ubuntu-release- Unapproved: google-cloud-sdk (artful-proposed/partner) [191.0.0-0ubuntu1~17.10.0 => 191.0.0-0ubuntu2~17.10.0] (no packageset)
[08:33] <xnox> slangasek, https://code.launchpad.net/~xnox/britney/crushing-failure-and-despair/+merge/340940
[08:33] <xnox> https://bugs.launchpad.net/britney/+bug/1753940
[08:33] <ubot5`> Ubuntu bug 1753940 in snapd (Ubuntu) "go vet causing Crushing failure and despair" [Undecided,New]
[08:34] <xnox> philroche, ^ that's the bug to watch.... a move on above, should make systemd migrate
[08:35] <sil2100> LocutusOfBorg: hey! re: virtualbox, https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1746316/comments/6
[08:35] <ubot5`> Ubuntu bug 1746316 in virtualbox (Ubuntu Artful) "[SRU] VirtualBox needs Security Patches" [Undecided,In progress]
[08:43] <cyphermox> could someone on the release team please review my MP?  https://code.launchpad.net/~cyphermox/britney/+git/britney2-ubuntu/+merge/340864
[08:43] <cyphermox> also, https://code.launchpad.net/~cyphermox/ubuntu-archive-tools/component-mismatches-mir/+merge/340939
[09:21] <slangasek> bashfulrobot: now having released to stable/ubuntu-18.04, you probably want to close that branch again so you don't have to do additional work to keep it in sync with stable :)
[09:57] <xnox> slangasek, do you not agree with merging https://code.launchpad.net/~xnox/britney/crushing-failure-and-despair/+merge/340940 ? please =)
[09:59] <Laney> it is merged
[10:13] <slangasek> + This package contains the debugging symbols for the Percona XtraDB Cluster binaries.
[10:13] <slangasek> jamespage: ^^ no new -dbg packages in Ubuntu for debug symbols; nack on this
[10:14] <slangasek> jamespage: ah; it's not a regression vs. percona 5.6, despite debian/control being reordered and largely undiffable.  But can we get this fixed with priority?
[10:19] -queuebot:#ubuntu-release- New: accepted percona-xtradb-cluster-5.7 [source] (bionic-proposed) [5.7.20-29.24-0ubuntu1]
[10:20] -queuebot:#ubuntu-release- Unapproved: accepted google-cloud-sdk [source] (artful-proposed) [191.0.0-0ubuntu2~17.10.0]
[10:22] -queuebot:#ubuntu-release- Unapproved: accepted google-cloud-sdk [source] (xenial-proposed) [191.0.0-0ubuntu2~16.04.0]
[10:22] -queuebot:#ubuntu-release- Unapproved: accepted google-cloud-sdk [source] (trusty-proposed) [191.0.0-0ubuntu2~14.04.0]
[10:43] -queuebot:#ubuntu-release- New binary: percona-xtradb-cluster-5.7 [s390x] (bionic-proposed/universe) [5.7.20-29.24-0ubuntu1] (no packageset)
[10:50] -queuebot:#ubuntu-release- New binary: percona-xtradb-cluster-5.7 [ppc64el] (bionic-proposed/universe) [5.7.20-29.24-0ubuntu1] (no packageset)
[10:57] -queuebot:#ubuntu-release- New binary: percona-xtradb-cluster-5.7 [amd64] (bionic-proposed/universe) [5.7.20-29.24-0ubuntu1] (no packageset)
[11:00] -queuebot:#ubuntu-release- New binary: percona-xtradb-cluster-5.7 [i386] (bionic-proposed/universe) [5.7.20-29.24-0ubuntu1] (no packageset)
[11:06] <xnox> Laney, but I am a twat and proposed invalid thing
[11:15] <Laney> naughty xnox
[11:37] -queuebot:#ubuntu-release- New binary: percona-xtradb-cluster-5.7 [armhf] (bionic-proposed/universe) [5.7.20-29.24-0ubuntu1] (no packageset)
[11:40] -queuebot:#ubuntu-release- New binary: percona-xtradb-cluster-5.7 [arm64] (bionic-proposed/universe) [5.7.20-29.24-0ubuntu1] (no packageset)
[12:10] <ginggs> would someone please bump in vorlon's hints? 'force-badtest r-cran-curl/3.1-2/arm64'
[12:26] <slangasek> ginggs: why, instead of disabling the test on arm64?
[12:27] <slangasek> ginggs: and why syncing a new version of the package that is identical to what I already had?
[12:36] <ginggs> slangasek: 1) I didn't notice it had previously failed on arm64 until after I uploaded. 2) So that other people don't have to spend time on it
[12:47] <slangasek> ginggs: I don't see why anyone would be spending any time on this, post-FF
[12:47] <slangasek> ginggs: including you
[12:48] <Odd_Bloke> doko: I was told to ping you about the Ruby transition; how close are we to all Ruby scripts using 2.5 by default in bionic?
[12:52] <Odd_Bloke> doko: I'm more-reliably-informed that I can bug other people instead, so never mind. :)
[14:11] <Odd_Bloke> xnox: http://paste.ubuntu.com/p/7Fc7bW29K8/
[14:13] <xnox> rbalint, ^
[14:51] <bashfulrobot> slangasek: sounds good. Appreciate the pointer (re: closing branch).
[14:56] -queuebot:#ubuntu-release- Unapproved: sahara-dashboard (xenial-proposed/universe) [4.0.0-1 => 4.0.0-1ubuntu1] (no packageset)
[16:10] -queuebot:#ubuntu-release- New source: golang-1.10 (artful-backports/primary) [1.10-1ubuntu1~17.10.1]
[16:10] -queuebot:#ubuntu-release- New source: golang-1.10 (xenial-backports/primary) [1.10-1ubuntu1~16.04.1]
[16:14] <Odd_Bloke> slangasek: xnox: If there's a specific autopkgtest that won't run on Ubuntu (for good reasons), is uploading an Ubuntu version that drops that test the appropriate thing to do?
[16:14] <nacc> Odd_Bloke: I've done that for some packages, I've also added a quilt patch that skips it with a reason, if possible
[16:18] <slangasek> Odd_Bloke: yes
[16:19] <bashfulrobot> @infinity: could you possibly kick off a build for Ubuntu budgie? We had to add a branch for our seeded snap package. But we couldn't kick it off from the QA ISO tracker.
[16:20] <slangasek> bashfulrobot: I'll take a look
[16:20] <bashfulrobot> Thanks!
[16:21] <Odd_Bloke> nacc: quilt patch patching debian/tests/foo?
[16:21] <bashfulrobot> slangasek: quick side question. These branches for seeded snaps. Are they just a one time thing for seeded snaps? Or what is the scenario in which these branches need to be created for seeded snaps?
[16:22] <nacc> Odd_Bloke: oh it depends on the tests, i meant like if the dep8 is just running upstream tests, they might be in the source
[16:22] <nacc> Odd_Bloke: if not, then no quilt patch, obviously
[16:22] <Odd_Bloke> Ah, OK, I didn't think so but was just checking.
[16:23] <Odd_Bloke> This is just a shell script; would deleting it be the right path, or adding an exit 0 with an explanatory comment?
[16:24] <nacc> Odd_Bloke: you're removing all the tests?
[16:25] <Odd_Bloke> nacc: There are two shell script tests; one of them is useful on Ubuntu, the other would require a multiverse package to run on Ubuntu.
[16:25] <Odd_Bloke> (This is vagrant, FWIW.)
[16:26] <slangasek> bashfulrobot: the branch needs to be opened for each Ubuntu release in order to create images for that release that include that snap
[16:27] <nacc> Odd_Bloke: ah I see; then yes, I imagine dropping it with a changelog entry is probably sufficient (is this debian delta?)
[16:27] <Odd_Bloke> Yeah, this would be delta from Debian.
[16:27] <Odd_Bloke> nacc: Cool, thanks for the guidance.
[16:27] <nacc> Odd_Bloke: yeah, that seems appropriate to me
[16:28] <Odd_Bloke> slangasek: So my next question, in the spirit of being thoughtful about packages are already in -proposed: Vagrant is currently failing due to the Ruby transition (as discussed at length :p), but the autopkgtests will continue to fail after that's resolved; I'm fixing that secondary failure.  Should I wait to upload until the first blockage is cleared?
[16:29] <bashfulrobot> slangasek: okay. Thank you for the clarification. So basically this would be a one-time thing for 18.04. And then a one-time thing for 18.10, and then another thing for 19.04 and forward. Per seeded snap. Open branch. Perform build. Remove branch. Got it.
[16:31] <slangasek> Odd_Bloke: I don't see any reason to wait.  Which source package is this for?  vagrant itself, or vagrant-mutate which blocks qemu?
[16:31] <Odd_Bloke> vagrant itself.
[16:31] <slangasek> bashfulrobot: exactly
[16:32] <slangasek> Odd_Bloke: yeah, vagrant/2.0.2+dfsg-2build1 isn't going anywhere on its own right now, no need to wait because it's not magically resolving itself in the near term.  *however*, we should trigger some --all-proposed retests of vagrant, either now or later
[16:32] <Odd_Bloke> Ack; just uploaded.
[16:33] <Odd_Bloke> cpaelzer: FYI: ^
[16:42] <Odd_Bloke> ruby-turbolinks could use a test rebuild with the ruby-defaults in -proposed.
[16:42] <bashfulrobot> slangasek:
[16:42] <bashfulrobot> perfect.
[16:42] <cpaelzer_> Odd_Bloke: slangasek: already triggered the all proposed test about two hours ago
[16:42] <bashfulrobot> have a great day. let me know if you need anythign else on the ISO build
[16:42] <cpaelzer_> checking results now ...
[16:43] <cpaelzer_> no new results in yet
[16:44] <slangasek> cpaelzer_: then I don't think you successfully triggered
[16:44] <slangasek> because queues are quite empty
[16:44] <cpaelzer_> yes I just checked the queues, it is not there
[16:45] <Odd_Bloke> This specific upload was also ~2 hours ago, so could have missed a retrigger anyway.
[16:45] <cpaelzer_> Odd_Bloke: it will not retrigger the test of "others"
[16:45] -queuebot:#ubuntu-release- New: accepted rax-nova-agent [amd64] (bionic-proposed) [2.1.12-0ubuntu2]
[16:46] <Odd_Bloke> cpaelzer_: Oh, the all-proposed test of vagrant?
[16:46] <cpaelzer_> I found it
[16:46] <cpaelzer_> Odd_Bloke: the rebuild of yours made the trigger target unavailable
[16:47] <slangasek> xnox: do you have any insight into whether the rails autopkgtest failure is broken test vs broken code?
[16:49] <cpaelzer_> in queue now slangasek / Odd_Bloke
[16:49] <Odd_Bloke> Thanks!
[16:49] <cpaelzer_> fixed my triggers to use the new vagrnat rebuild properly (all-proposed takes care of that anyway)
[16:49] <cpaelzer_> so test should (tm) succeed and qemu be good for now
[16:57] -queuebot:#ubuntu-release- New: accepted golang-1.10 [source] (artful-backports) [1.10-1ubuntu1~17.10.1]
[16:57] -queuebot:#ubuntu-release- New: accepted golang-1.10 [source] (xenial-backports) [1.10-1ubuntu1~16.04.1]
[16:58] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Bionic Beta 1] (20180307) has been added
[16:58] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop i386 [Bionic Beta 1] (20180307) has been added
[17:05] -queuebot:#ubuntu-release- New binary: golang-1.10 [i386] (artful-backports/universe) [1.10-1ubuntu1~17.10.1] (no packageset)
[17:06] -queuebot:#ubuntu-release- New binary: golang-1.10 [s390x] (artful-backports/universe) [1.10-1ubuntu1~17.10.1] (no packageset)
[17:07] -queuebot:#ubuntu-release- New binary: golang-1.10 [s390x] (xenial-backports/universe) [1.10-1ubuntu1~16.04.1] (no packageset)
[17:08] -queuebot:#ubuntu-release- New binary: golang-1.10 [ppc64el] (artful-backports/universe) [1.10-1ubuntu1~17.10.1] (no packageset)
[17:09] -queuebot:#ubuntu-release- New binary: golang-1.10 [ppc64el] (xenial-backports/universe) [1.10-1ubuntu1~16.04.1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: golang-1.10 [amd64] (artful-backports/universe) [1.10-1ubuntu1~17.10.1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: golang-1.10 [amd64] (xenial-backports/universe) [1.10-1ubuntu1~16.04.1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: golang-1.10 [i386] (xenial-backports/universe) [1.10-1ubuntu1~16.04.1] (no packageset)
[17:18] <cpaelzer> slangasek: on the seed changes, just today we realized that openbsd-inetd should also be demoted
[17:18] <cpaelzer> it has nothing holding it in main than the seed itself
[17:18] <cpaelzer> and all it did in the past is no more important
[17:19] <cpaelzer> so I'll make this part of the MP as well
[17:19] <cpaelzer> if you have concerns, please let me know
[17:19] -queuebot:#ubuntu-release- New binary: golang-1.10 [arm64] (artful-backports/universe) [1.10-1ubuntu1~17.10.1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: golang-1.10 [arm64] (xenial-backports/universe) [1.10-1ubuntu1~16.04.1] (no packageset)
[17:20] <acheronuk> [23:43] <mwhudson> tsimonq2: ok, the canonical vcs is the ubuntu archive!!
[17:20] <acheronuk> a bit hard to do a merge request against that in lp
[17:22] <acheronuk> I guess a bug report and debdiff them
[17:22] <acheronuk> *then
[17:22] -queuebot:#ubuntu-release- New binary: golang-1.10 [armhf] (artful-backports/universe) [1.10-1ubuntu1~17.10.1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: golang-1.10 [armhf] (xenial-backports/universe) [1.10-1ubuntu1~16.04.1] (no packageset)
[17:26] <tsimonq2> acheronuk: git-ubuntu, hint hint
[17:26]  * tsimonq2 nudges nacc
[17:26] <tsimonq2> :)
[17:26] <nacc> tsimonq2: yeah yeah yeah
[17:26] <nacc> tsimonq2: we're doing a 1% phasing of main right now
[17:26] <nacc> (currenlty reimporting everything in our whitelist + 1% of main)
[17:27] <acheronuk> tsimonq2: lol. I knew someone would pipe up with that!
[17:27] <nacc> depending on how that goes (it's progressing nicely, but will take a few more days to finish)
[17:27] <nacc> we'll up the phasing to 2% next week :)
[17:27] <tsimonq2> nacc: Ah ok. ooc, how do you determine these percentages?
[17:28] <Odd_Bloke> slangasek: Also: https://github.com/rails/rails/commit/be9dc78fccc80bb5045c67b435b5c7e36ea8a296
[17:28] <acheronuk> tsimonq2: (done/notdone)*100
[17:28]  * acheronuk hides
[17:29] <nacc> tsimonq2: determine as in which way? the value of them (we specify it to the scripts) or what they mean (md5sum(srcpkg name) < phasing percentage * 2^128, just like the -updates phasing)
[17:29] <nacc> tsimonq2: the 1% is to see how the phasing affects the package count, as well as time, and space on Launchpad
[17:29] <tsimonq2> Ah ok
[17:29] <nacc> we also have a blacklist and whitelist, so the phasing percentage is not a direct indicator yet
[17:30] <nacc> but our short-term goal is 100% of main
[17:30] <tsimonq2> But like, 1% from an alphabetical list? How is this sorted?
[17:30] <tsimonq2> Ah ok
[17:30] <nacc> tsimonq2: no sorting necessary
[17:30] <nacc> tsimonq2: md5sum(srcpkg name) is a numerical value
[17:30] <nacc> tsimonq2: compare that to 1% of 2^128
[17:30] <nacc> and statistically we get ~1% of all source packages, assuming a relatively even distribution (not entirely true, but is an approximation)
[17:31] <nacc> actually, i think md5sum might be relatively uniform
[17:31] <tsimonq2> Huh ok
[17:31] <nacc> (2^128 being the maximum md5sum)
[17:32] <tsimonq2> nacc: Seems like an algorithm that has a name... what might that be? :)
[17:32] <nacc> tsimonq2: https://wiki.ubuntu.com/PhasedUpdates
[17:32] <nacc> tsimonq2: update-manager section
[17:36] <tsimonq2> Interesting.
[17:36] <tsimonq2> OK, cool.
[19:26] <wxl> bashfulrobot: you think you're going to be able to get all your testing in before end ot the day or are you thinking a late release thursday (or a potential delay, whcih might be good for kubuntu)?
[19:30] <wxl> oh jeez no lubuntu next images. i trust i need to get you to add them, infinity?
[19:42] <infinity> wxl: Oh, I assumed Next wasn't happening for milestones, since we'd discussed that it probably shouldn't happen for release.  I can add it for the Beta and spin 'em up.
[19:43] <wxl> infinity: it looks like we had them for milestones only for artful, so i think we're on the same page there.
[19:44] <infinity> wxl: Building now.
[19:44] <wxl> infinity: thank you, sir :)
[19:44] <infinity> (Well, in one minute when the rebuild job ticks over)
[19:46] <infinity> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/bionic/lubuntu-next
[19:48] <wxl> infinity: don't they usually show on the tracker as being in a building state?
[19:49] <infinity> wxl: It does on the daily milestone.   It won't show at all on the Beta milestone until one has been built (this one) :P
[19:49] <wxl> infinity: weird behavior, but ok :)
[19:50] <infinity> wxl: Well, I could have done it in a different order by adding one of the older images to the beta milestone and then triggering the rebuild, which would give you the output you expected.
[19:50] <infinity> wxl: But I don't like adding an image to a milestone for the express purpose of obsoleting it seven seconds later.
[19:50] <infinity> (Both for reasons of confusion and efficiency)
[19:51] <wxl> infinity: sounds like the behavior is no different, but it's less obvious with the dailies.
[19:52] -queuebot:#ubuntu-release- Unapproved: systemd (trusty-proposed/main) [204-5ubuntu20.26 => 204-5ubuntu20.27] (core)
[19:53] <infinity> wxl: It perhaps helps if you realise there's no difference between "daily" and "milestone", except that when a milestone is active, any daily built that's listed in the manifest *also* gets posted to the milestone.
[19:53] <infinity> wxl: So, I added next to the manifest, triggered a daily rebuild, and when it posts, it'll show up on both.
[19:53] <wxl> infinity: yeah, that's whta i was alluding to.
[19:54] <wxl> infinity: i'll quit bothering you now :)
[20:17] <bashfulrobot> wxl: we are literally just having a discussion about this. There are some pros to delaying since our ISO was just built today due to a delay with a snap seed. I'm just confirming with our team lead.
[20:18] -queuebot:#ubuntu-release- Builds: Lubuntu Next Desktop amd64 [Bionic Beta 1] (20180307) has been added
[20:18] -queuebot:#ubuntu-release- Builds: Lubuntu Next Desktop i386 [Bionic Beta 1] (20180307) has been added
[20:32] <wxl> bashfulrobot: alright. ping me when you get it figured out, please?
[20:40] <infinity> bashfulrobot: If there's a delay, I assume it would just be a day, right?
[20:40] <infinity> bashfulrobot: I'm fine with releasing on Friday instead of Thursday.  Don't want to keep the soft freeze in place much longer than that.
[20:59] <bashfulrobot> infinity:  I think so. I wouldn't want to delay any later than that.
[20:59] <bashfulrobot> wxl: absolutely.
[21:39] <bashfulrobot> ok, wxl, infinity
[21:39] <bashfulrobot> tsimonq2:
[21:40] <bashfulrobot> Are we all in agreement to delay until Friday eve?
[21:42] <tsimonq2> ACK.
[21:43] <bashfulrobot> ACK on our part.
[21:43] <bashfulrobot> Just had to respin our ISo due to a bug in our snap
[21:51] <bashfulrobot> Quick Q - is this the right place to request permissions to http://iso.qa.ubuntu.com/qatracker (to trigger a new build)? Right now fossfreedom is the only one who can do this on behalf of ubuntu Budgie.
[21:54] <bashfulrobot> tsimonq2 / infinity ^^ You fine gents may know the answer. 😃
[21:55] <tsimonq2> bashfulrobot: There's an LP team you need to be added to.
[21:55] <flexiondotorg> bashfulrobot infinity Ubuntu MATE have expressed our intention to participate in Beta 1 bit we don't have isos.
[21:56] <flexiondotorg> Can anything be done to spin them please?
[21:56] <bashfulrobot> infinity: had the traditional nusakan stuff been done for mate? Can we squeek that in?
[21:57] <bashfulrobot> flexiondotorg: FYI - we are likely deferring beta until Friday evening (FYI).
[21:57] <jbicha> infinity: today's ISO builds still identify as Alpha in their metadata
[21:59] <flexiondotorg> We can certainly bo the QA by Friday. So if iso can be produced we've got the QA team ready.
[22:01] -queuebot:#ubuntu-release- New binary: linux [s390x] (bionic-proposed/main) [4.15.0-12.13] (core, kernel)
[22:01]  * bashfulrobot defers to infinity for nusakan setup.
[22:04] <bashfulrobot> tsimonq2: Who admins that team?
[22:06] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Bionic Beta 1] has been updated (20180307.1)
[22:06] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop i386 [Bionic Beta 1] has been updated (20180307.1)
[22:07] <tsimonq2> bashfulrobot: I think you can generally assume ~ubuntu-cdimage members that work for Canonical.
[22:07] <bashfulrobot> ty
[22:10] <bashfulrobot> slangasek: I noticed that you are a member of the cd-image team - are you guys the right people to request access to http://iso.qa.ubuntu.com/qatracker?
[22:11] <bashfulrobot> Well access in the capacity to generate rebuilds on the ISO
[22:11] <bashfulrobot> not just login for review
[22:13] <bashfulrobot> slangasek: I know you are at the sprint - so this is not critical, nor a blocker.
[22:16] <bashfulrobot> slangasek: when you happen to read this - ideally we would like to make https://launchpad.net/~ubuntu-budgie-release a member, however if there is a policy against nesting a group (maybe security concerns), could we add myself?
[22:17] <bashfulrobot> fossfreedom might be handy to pop an "aye" in here for approval to do so on behalf of Ubuntu Budgie.
[22:22] <infinity> jbicha: Yeah, not fussed about them saying Alpha, that's not worth invalidating all the testing.
[22:22] <infinity> flexiondotorg: I can add MATE.  On Tuesday, when I set it up, you hadn't responded.
[22:23] <infinity> flexiondotorg: In fact, you still haven't responded to the thread asking who was participating, so not sure where it was expressed.
[22:27] <flexiondotorg> infinity: Thanks for adding MATE. I had told tsimonq2 that we wanted to participate, sorry that wasn't the correct route.
[22:28] <infinity> flexiondotorg: He isn't the one doing the paperwork bits, so less helpful. ;)
[22:32] <infinity> flexiondotorg: Uncronned and added.
[22:32] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Bionic Beta 1] (20180307.1) has been added
[22:32] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Bionic Beta 1] (20180307.1) has been added
[22:35] <infinity> bashfulrobot: You should be able to trigger rebuilds now.  Use this power wisely (ie: sparingly).
[22:40] <bashfulrobot> Thank you Infinity!!! Was that team granted access, or my user directly?
[22:41] <infinity> bashfulrobot: Your user.
[22:42] <tsimonq2> flexiondotorg: Ah, I thought you had communicated this back to the Release Team already. Apologies.
[22:47] <flexiondotorg> infinity tsimonq2 My screw up. I'll do better. Thanks for adding Ubuntu MATE
[22:47] <infinity> bashfulrobot: A few things.  Don't request rebuilds willy-nilly.  Invalidating all your testing because someone uploaded a spelling correction isn't nice.  Never request a rebuild for something in re-building status.  It'll wedge things.  And, uhm.  That's about it, I guess.
[22:47]  * infinity is going to see if a nap fixes his headache.
[22:47] <infinity> If the world explodes while I'm gone, I'll put it back together when I get back.
[22:51] <bashfulrobot> infinity: thank you very much
[22:54] -queuebot:#ubuntu-release- New binary: linux [ppc64el] (bionic-proposed/main) [4.15.0-12.13] (core, kernel)