[00:00] <doko> RAOF: I'd like to see that.  please could you file a bug report somewhere to channel that discussion?
[00:01] <RAOF> doko: Any idea where? Is there a brittney project in LP?
[00:03] <RAOF> Maybe I'll just start a thread on the mailing list.
[00:04] <doko> RAOF: well, file a bug report, and then let somebody reassign it. maybe cjwatsonor slangasek could help out with the correct package
[00:11] <infinity> RAOF: I think your bug is https://bugs.launchpad.net/britney/+bug/1700668
[00:20] <acheronuk> what s390x changes happened exactly?
[00:20] <xnox> acheronuk, pull RAM stick out; push bigger RAM stick in
[00:21] <acheronuk> no speed ups or increase in parallelisation then?
[00:21] <xnox> acheronuk, unless you mean autopkgtests used to run in containers and report "pass" when in fact it should have been "always failed"
[00:21] <xnox> and now it uses kvm VMs from openstack to run the tests.
[00:22] <xnox> acheronuk, the mainframe is the same, otherwise.
[00:22] <acheronuk> nah. getting a build fail. which I suspect is rubbish cmake nor being able to cope with parallel build on such a fast machine
[00:23] <acheronuk> had similar before with a different package
[00:24] <acheronuk> must be the code regressed
[00:29] -queuebot:#ubuntu-release- New binary: pytest-astropy [amd64] (bionic-proposed/universe) [0.2.1-1] (no packageset)
[00:30] -queuebot:#ubuntu-release- New: accepted pytest-astropy [amd64] (bionic-proposed) [0.2.1-1]
[00:43] <slangasek> elopio: I have one level of timeout configuration in autopkgtest-cloud; which architectures need this?
[00:45] <slangasek> elopio: the log of snapcraft 2.39+18.04.7 doesn't look like timeouts to me https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/snapcraft/20180201_121158_ca989@/log.gz
[00:46] <slangasek> elopio: if these are upstream tests, I don't know how to configure a different timeout for those, but the answer would lie somewherehttps://git.launchpad.net/autopkgtest-cloudfg in
[00:47] <slangasek> elopio: if these are upstream tests, I don't know how to adjust those, but the answer would lie somewhere in https://git.launchpad.net/autopkgtest-cloud and I could land a patch if someone implemented it
[00:56] <sil2100> acheronuk: yeah, still on my plate, sadly our weekly report seems to not work and running the script is not as easy as I'd expect, it crashes here
[00:56] <sil2100> acheronuk: so I'll just have to look into it in detail tomorrow
[00:57] <sil2100> Today it's too late for me to dig deeper
[00:57] <acheronuk> sil2100: ok. no problem
[00:57] <sil2100> Always hated running this report script, always had crashes, was so happy to see the automated weekly e-mails
[00:57] <sil2100> But those aren't happening anymore
[00:58]  * sil2100 goes to sleep
[00:58] <sil2100> o/
[01:21] <RAOF> Huh. Is bazaar.launchpad.net down?
[01:21] <wxl> i can connect to it if that's what you mean
[01:23] <wxl> and i can browse some code there
[01:28] <RAOF> Ah! There we go. *Now* bzr connects.
[01:29] <RAOF> Oh, no.
[01:29] <RAOF> Different ssh process flashing the yubikey :(
[01:43] <elopio> slangasek: it's for the tests in https://github.com/snapcore/snapcraft/pull/1908
[01:43] <slangasek> right
[01:43] <elopio> this one should get autopkgtest to green. But I'm  not sure even the last split would get arm64 to fix in the current timeout
[01:44] <slangasek> elopio: so, worker-config-production/ supports marking certain tests as 'long_tests'.  But I don't think there's a hook here currently for upstream tests.  So this would need extending
[01:45] <elopio> well, the current urgent thing is to get them green after sergiusens dput's this. To be able to release 2.39
[01:46] <slangasek> elopio: ok, for the package tests in the Ubuntu archive, that's just a config change (hopefully - hopefully doubling the timeout is sufficient!)
[01:46] <slangasek> elopio: which archs are you currently hitting the timeout on?
[01:47] <slangasek> (I don't have a good way to see this through the autopkgtest reporting UI for upstream tests, or I'd look it up myself)
[01:47] <elopio> slangasek: arm64. I will confirm to you if my latest split solves it for amd64 in a couple of hours.
[01:47] <slangasek> elopio: ok.  if you need me to bump the timeout, just let me know
[01:47] <elopio> slangasek: I will. Are you close to EOD? Better ping tomorrow?
[01:48] <slangasek> elopio: my IRC client never sleeps
[01:48] <slangasek> elopio: and I'm sure to be checking it at some point this evening
[01:52] <elopio> slangasek: alright, thanks!
[02:07] -queuebot:#ubuntu-release- New binary: gcc-8 [s390x] (bionic-proposed/universe) [8-20180207-1ubuntu1] (no packageset)
[02:42] -queuebot:#ubuntu-release- New binary: gcc-8 [ppc64el] (bionic-proposed/universe) [8-20180207-1ubuntu1] (no packageset)
[04:42] -queuebot:#ubuntu-release- New binary: gcc-8 [arm64] (bionic-proposed/universe) [8-20180207-1ubuntu1] (no packageset)
[05:14] -queuebot:#ubuntu-release- New binary: cypari2 [s390x] (bionic-proposed/universe) [1.1.4-2] (no packageset)
[05:15] -queuebot:#ubuntu-release- New binary: cypari2 [amd64] (bionic-proposed/universe) [1.1.4-2] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: cypari2 [i386] (bionic-proposed/universe) [1.1.4-2] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: gcc-8 [armhf] (bionic-proposed/universe) [8-20180207-1ubuntu1] (no packageset)
[05:19] -queuebot:#ubuntu-release- New binary: cypari2 [ppc64el] (bionic-proposed/universe) [1.1.4-2] (no packageset)
[05:26] <slangasek> doko: why is it correct to ignore the timezone failures for ruby2.3?  whose timezone handling is wrong, ruby's or tzdata's?
[05:29] -queuebot:#ubuntu-release- New binary: cypari2 [armhf] (bionic-proposed/universe) [1.1.4-2] (no packageset)
[05:45] -queuebot:#ubuntu-release- New binary: cypari2 [arm64] (bionic-proposed/universe) [1.1.4-2] (no packageset)
[05:57] -queuebot:#ubuntu-release- New: accepted cypari2 [amd64] (bionic-proposed) [1.1.4-2]
[05:57] -queuebot:#ubuntu-release- New: accepted cypari2 [armhf] (bionic-proposed) [1.1.4-2]
[05:57] -queuebot:#ubuntu-release- New: accepted cypari2 [ppc64el] (bionic-proposed) [1.1.4-2]
[05:57] -queuebot:#ubuntu-release- New: accepted cypari2 [arm64] (bionic-proposed) [1.1.4-2]
[05:57] -queuebot:#ubuntu-release- New: accepted cypari2 [s390x] (bionic-proposed) [1.1.4-2]
[05:57] -queuebot:#ubuntu-release- New: accepted cypari2 [i386] (bionic-proposed) [1.1.4-2]
[08:33] <doko>      Japanese DST transitions (1948-1951) were Sundays at 00:00, not
[08:33] <doko>      Saturdays or Sundays at 02:00.  (Thanks to Takayuki Nikai.)
[08:33] <doko> slangasek: ^^^ Debian #889046, so yes, it's an issue, but a minor one
[08:34] <doko> and we don't care about 2.3 anymore
[09:43] <cpaelzer> doko: thanks for the override to main with htop
[09:43] <cpaelzer> the reason it didn't show up yet was that I waited for an ack on https://code.launchpad.net/~paelzer/ubuntu-seeds/18.04-support-htop/+merge/337201
[09:43] <cpaelzer> which is more for the process, I think the change is fine
[09:44] <cpaelzer> I think I might push the change, now that you have done the override
[09:58] <doko> tcl8.6 migrated. looks like we can demote ruby soonish
[10:44] <LocutusOfBorg> xnox, FYI I did the haskell rebuilds for new openssl default
[10:47] <xnox> LocutusOfBorg, thanks!
[10:49] <LocutusOfBorg> yw :)
[10:49] <LocutusOfBorg> to be honest, I was wondering what did make them needed, and I discovered openssl just after having issued the first one :p
[10:49] <LocutusOfBorg> (specially because we blacklisted haskell days ago)
[11:48] -queuebot:#ubuntu-release- New binary: omniorb-dfsg [s390x] (bionic-proposed/universe) [4.2.2-0.6] (no packageset)
[11:51] -queuebot:#ubuntu-release- New binary: omniorb-dfsg [i386] (bionic-proposed/universe) [4.2.2-0.6] (no packageset)
[11:54] -queuebot:#ubuntu-release- New binary: omniorb-dfsg [ppc64el] (bionic-proposed/universe) [4.2.2-0.6] (no packageset)
[12:02] -queuebot:#ubuntu-release- New binary: omniorb-dfsg [amd64] (bionic-proposed/universe) [4.2.2-0.6] (no packageset)
[12:14] -queuebot:#ubuntu-release- New binary: omniorb-dfsg [armhf] (bionic-proposed/universe) [4.2.2-0.6] (no packageset)
[12:15] -queuebot:#ubuntu-release- New binary: omniorb-dfsg [arm64] (bionic-proposed/universe) [4.2.2-0.6] (no packageset)
[12:16] -queuebot:#ubuntu-release- New binary: gcc-8 [s390x] (bionic-proposed/universe) [8-20180207-2ubuntu1] (no packageset)
[12:20] -queuebot:#ubuntu-release- New: accepted omniorb-dfsg [amd64] (bionic-proposed) [4.2.2-0.6]
[12:20] -queuebot:#ubuntu-release- New: accepted omniorb-dfsg [armhf] (bionic-proposed) [4.2.2-0.6]
[12:20] -queuebot:#ubuntu-release- New: accepted omniorb-dfsg [ppc64el] (bionic-proposed) [4.2.2-0.6]
[12:20] -queuebot:#ubuntu-release- New: accepted omniorb-dfsg [arm64] (bionic-proposed) [4.2.2-0.6]
[12:20] -queuebot:#ubuntu-release- New: accepted omniorb-dfsg [s390x] (bionic-proposed) [4.2.2-0.6]
[12:20] -queuebot:#ubuntu-release- New: accepted omniorb-dfsg [i386] (bionic-proposed) [4.2.2-0.6]
[12:53] -queuebot:#ubuntu-release- New binary: gcc-8 [ppc64el] (bionic-proposed/universe) [8-20180207-2ubuntu1] (no packageset)
[13:04] <xnox> slangasek, running tests against matching build-deps helps with test, so openssl/openssl1.0 are now less red. Now need to wait for arm64 to catch up.
[13:11] -queuebot:#ubuntu-release- New binary: gcc-8 [i386] (bionic-proposed/universe) [8-20180207-2ubuntu1] (no packageset)
[13:31] <jbicha> please remove the valadoc source package, it has been merged into the vala source
[13:44] <rbasak> jbicha: I'm not sure if you're already aware, but the normal way to request that is to file a bug, subscribe ~ubuntu-archive, and wait until they batch process those. Unless there's some reason it blocks something else.
[13:57] <jbicha> rbasak: it shows up on https://people.canonical.com/~ubuntu-archive/nbs.html is all
[13:58] <jbicha> I've filed lots of removal bugs. I can file one more if you want me to :)
[13:58] <rbasak> Oh
[13:58] <rbasak> I don't think NBS needs a specific bug.
[13:58] <rbasak> Archive admins notice those when they want to care (once a cycle?) :)
[13:58] <jbicha> nbs is processed fairly often
[13:59] <jbicha> at least the easy ones are
[14:07] <apw> nbs for devel gets processed at least once a day
[14:08] <apw> jbicha, but are you saying that the valadoc source package is dead ?
[14:10] <apw> as that would not be NBS in any sense
[14:12] <apw> well valadoc is depending on something NBS but that doesn't make it NBS per-see
[14:13] -queuebot:#ubuntu-release- Unapproved: accepted partman-partitioning [source] (xenial-proposed) [110ubuntu4.2]
[14:14] <apw> jbicha, if you would file me a removal bug i can make that go away
[14:14] -queuebot:#ubuntu-release- Unapproved: accepted partman-partitioning [source] (artful-proposed) [114ubuntu3]
[14:15] -queuebot:#ubuntu-release- Unapproved: accepted partman-partitioning [source] (trusty-proposed) [99ubuntu2]
[14:17] -queuebot:#ubuntu-release- Unapproved: accepted preseed [source] (xenial-proposed) [1.71ubuntu1.2]
[14:18] -queuebot:#ubuntu-release- Unapproved: accepted preseed [source] (trusty-proposed) [1.62ubuntu1.2]
[14:19] <xnox> slangasek, horum... curl openssl1.1 change got reverted, as they are debating how to handle abi transition and complete curl4 soname change, etc....
[14:37] <xnox> slangasek, could we somehow force drain arm64/huge queue in adt? more builders? make it a priority? things keep trumping it, and it fails to "upscore" up.
[14:48] <jbicha> apw: LP: #1747931 thanks
[14:53] -queuebot:#ubuntu-release- Packageset: 85 entries have been added or removed
[15:00] -queuebot:#ubuntu-release- Unapproved: gnome-disk-utility (xenial-proposed/main) [3.18.3.1-1ubuntu1 => 3.18.3.1-1ubuntu1.1] (ubuntu-desktop)
[15:08] -queuebot:#ubuntu-release- Packageset: Removed esound from kubuntu in bionic
[15:08] -queuebot:#ubuntu-release- Packageset: Removed kdevplatform from kubuntu in bionic
[15:09] -queuebot:#ubuntu-release- Packageset: Removed libkmahjongg from kubuntu in bionic
[15:09] -queuebot:#ubuntu-release- Packageset: Removed llvm-toolchain-4.0 from kubuntu in bionic
[15:09] -queuebot:#ubuntu-release- Packageset: Removed konsole4 from kubuntu in bionic
[15:09] -queuebot:#ubuntu-release- Packageset: Removed pygobject-2 from kubuntu in bionic
[15:09] -queuebot:#ubuntu-release- Packageset: Removed kate4 from kubuntu in bionic
[15:09] -queuebot:#ubuntu-release- Packageset: Removed pygtk from kubuntu in bionic
[15:09] -queuebot:#ubuntu-release- Packageset: Removed sysstat from kubuntu in bionic
[15:09] -queuebot:#ubuntu-release- Packageset: Removed yaml-cpp0.3 from kubuntu in bionic
[15:09] -queuebot:#ubuntu-release- Packageset: Removed py3cairo from kubuntu in bionic
[15:09] -queuebot:#ubuntu-release- Packageset: Removed xplc from kubuntu in bionic
[15:09] -queuebot:#ubuntu-release- Packageset: Removed libqaccessibilityclient from kubuntu in bionic
[15:21] <Odd_Bloke> infinity: slangasek: My artful upload of vagrant didn't update the maintainer field; is that worthy of a reupload to fix?
[15:21] <Odd_Bloke> (cpaelzer: ^)
[15:24] <sil2100> Odd_Bloke: it usually depends on the person doing the review - as it got accepted already into -proposed I personally woudln't request a re-upload
[15:24] <sil2100> If it would still be in the queue, yes, but when it's in -proposed well, it's not nice but not serious enough IMO - it's it's just the control file maintainer part
[15:25] -queuebot:#ubuntu-release- New binary: gcc-8 [amd64] (bionic-proposed/universe) [8-20180207-2ubuntu1] (no packageset)
[15:25] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (artful-proposed/main) [4.13.0-33.36] (core, kernel)
[15:28] <cpaelzer> Odd_Bloke: which is essentially what I said - I wasn't sure on how serious it would be seen, but seeing "not serious enough" by sil2100 seems ok then
[15:31] <Odd_Bloke> cpaelzer: \o/
[15:32] <Odd_Bloke> cpaelzer: So my next question is this: can I make the change and leave it somewhere in the git-ubuntu branches so (if the next uploader uses git-ubuntu) it will be picked up in the next upload?
[15:34] <cpaelzer> Odd_Bloke: not really that I'd know how
[15:34] <cpaelzer> Odd_Bloke: but having it in your branch pushed is useful
[15:34] <cpaelzer> I usually check git ubuntu remote add <lastuploader>
[15:34] <cpaelzer> which is kind of nice, as you'll see what he has done
[15:34] <cpaelzer> you can pick up things like this form there
[15:35] <cpaelzer> but not official part of the process, just best practise
[15:35] <cpaelzer> Odd_Bloke: you might ask rbasak and nacc if there is a thought on storing interim commits in an accessible way (I don't tihnk so)
[15:35] <rbasak> We don't have a solution for that right now.
[15:36] <rbasak> You could store it anywhere right now. I suppose we could do with defining a place for other develoeprs to look if they wish. It doesn't even have to be official.
[15:37] <rbasak> Right now you can find branches, for example Odd_Bloke's repo, in https://code.launchpad.net/ubuntu/+source/vagrant/+git
[15:37] <rbasak> But what we're missing is some kind of "look here before uploading" marker.
[15:38] <rbasak> We could have the lint tool identify that too perhaps.
[15:40] -queuebot:#ubuntu-release- New binary: gcc-8 [armhf] (bionic-proposed/universe) [8-20180207-2ubuntu1] (no packageset)
[15:43] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (artful-proposed) [4.13.0-33.36]
[15:44] <nacc> Odd_Bloke: like a partial NMU
[15:53] -queuebot:#ubuntu-release- New binary: gcc-8 [arm64] (bionic-proposed/universe) [8-20180207-2ubuntu1] (no packageset)
[15:59] -queuebot:#ubuntu-release- Unapproved: util-linux (xenial-proposed/main) [2.27.1-6ubuntu3.4 => 2.27.1-6ubuntu3.5] (core)
[16:08] -queuebot:#ubuntu-release- Unapproved: gnome-disk-utility (artful-proposed/main) [3.26.1-0ubuntu1 => 3.26.1-0ubuntu1.1] (ubuntu-desktop)
[16:12] <juliank> I think the util-linux upload ^^ is kind of blocked on autopkgtest regressions (?) from the fix for bug 1722313 that's stuck in proposed.
[16:15] <doko> now ruby-rspec breaks the ruby2.3 tests. can we just ignore all ruby2.3 related autopkg test failures? it will go away anyway
[16:50] -queuebot:#ubuntu-release- Unapproved: bamf (xenial-proposed/main) [0.5.3~bzr0+16.04.20160824-0ubuntu1 => 0.5.3~bzr0+16.04.20180207-0ubuntu1] (ubuntu-desktop) (sync)
[16:51] -queuebot:#ubuntu-release- Unapproved: libunity (xenial-proposed/main) [7.1.4+16.04.20160701-0ubuntu1 => 7.1.4+16.04.20180207-0ubuntu1] (kubuntu, ubuntu-desktop) (sync)
[16:58] <Trevinho> rbasak: hey, if you've still some time please give a check to the SRUs for bamf, libunity on X that are in queue. Thanks.
[17:07] <slangasek> doko: are we sure it will go away?  (also, yes, you could've asked this question before reuploading ruby2.3 ;)
[17:10] <doko> ;)
[17:10] <doko> well yes, I only saw the new build failures after the ruby-rspec upload
[17:11] <slangasek> xnox: queues> sorry, it's diminishing returns to force-drain this queue when all of these tests eventually need to get run.  When I looked last night it appeared it might zero out in about 24h.  I'm oiling the machine again this morning.
[17:11] <doko> will it go away? I would hope so, and and will demote hopefully
[17:12] <slangasek> doko: searching update_excuses for ruby2.3, I don't see any ruby-rspec-related failures.  Is this in ruby-rspec-{rails,retry}?
[17:14] <doko> hmm, this morning I still saw two. so nevermind about that
[17:39] <slangasek> ppc64el autopkgtest runners were having a bad day.  should be fixed now.
[17:40] <nacc> slangasek: thanks!
[17:41] -queuebot:#ubuntu-release- Unapproved: vagrant (xenial-proposed/universe) [1.8.1+dfsg-1 => 1.8.1+dfsg-1ubuntu0.1] (ubuntu-cloud)
[17:50] <nacc> slangasek: if a package is marked as 'published'
[17:51] <nacc> but not yet in rmadison, am i safe to retrigger dependent rebuilds? or should i wait for rmadison?
[17:52] <slangasek> nacc: the 'published' flag is set in the lp database and happens before the publication is complete, even to ftpmaster.internal.  So you would be racing
[17:52] <nacc> slangasek: ah ok, i'll wait then
[17:52] <nacc> yeah i was confused by that myself earlier, so that matches what I saw
[17:58] -queuebot:#ubuntu-release- Unapproved: accepted vagrant [source] (xenial-proposed) [1.8.1+dfsg-1ubuntu0.1]
[19:32] <nacc> xnox: do libargon and libsodium's presence on a system change gpg's behavior?
[19:40] <nacc> xnox: or maybe you can help me figure out the ftbfs of php-crypt-gpg?
[19:40] <nacc> only happens with proposed enablled
[20:01] -queuebot:#ubuntu-release- Unapproved: gcc-7 (artful-proposed/main) [7.2.0-8ubuntu3.1 => 7.2.0-8ubuntu3.2] (core) (sync)
[20:01] -queuebot:#ubuntu-release- Unapproved: gcc-5 (xenial-proposed/main) [5.4.0-6ubuntu1~16.04.8 => 5.4.0-6ubuntu1~16.04.9] (core) (sync)
[20:12] <tsimonq2> slangasek: can I please get a pull + mirror deploy on Lubuntu's cdimage includes?
[20:15] -queuebot:#ubuntu-release- Unapproved: gcc-5-cross (xenial-proposed/main) [24ubuntu0.2 => 24ubuntu0.3] (ubuntu-desktop) (sync)
[20:16] -queuebot:#ubuntu-release- Unapproved: gcc-5-cross-ports (xenial-proposed/universe) [10ubuntu0.1 => 10ubuntu0.2] (no packageset) (sync)
[20:18] <nacc> slangasek: any idea what's goingn on with 'huge arm64's queue? it's up to 1362
[20:18] <nacc> slangasek: and is the last thing blocking php7.2 itself :/
[20:21] <tyhicks> FYI, the gcc-7, gcc-5, gcc-5-cross, and gcc-5-cross-ports syncs are binary copies from ubuntu-security-proposed to the respective -proposed pockets and we (Ubuntu Security) will copy them to the respective -security pockets next week
[20:21] <slangasek> nacc: it's not up to 1362, it's down to 1362. https://cloud.kpi.canonical.com/dashboard/db/ubuntu-foundations?panelId=19&fullscreen
[20:22] <slangasek> nacc: arm64 runners are chugging away at the backlog as fast as they can
[20:25] <nacc> slangasek: touche
[20:27] <slangasek> nacc: note that this is still the backlog from the meltdown downtime.  we've thrown a lot of capacity at it, and it's not the fastest arch but it's been steadily closing the gap... so we should be down to a 1-2 day lag by EOD today, and hopefully have caught up to the other archs by EOD tomorrow
[20:27] <nacc> slangasek: ok, that's good to know
[20:27] <nacc> a lot of stuff in b-p is blocked on php7.2, even once i get their tests to pass, i expect
[20:30] <slangasek> nacc: there's definitely a few things in that queue that I'm anxious to see get through their tests.  systemd, openssl1.0, openssl...
[20:30] <nacc> slangasek: should ppc64el be caught up by then too?
[20:31] <slangasek> none of which I want to just blindly ignore test results on
[20:31] <nacc> slangasek: yeah, we have a bit of a perfect storm
[20:31] <slangasek> nacc: yes, ppc64el had a one-off infra bug that was killing runners because bos02 was missing the artful images.  It should make quick work of the backlog
[20:32] <nacc> slangasek: ah great
[20:33] <slangasek> (ppc64el backlog is actually down 12% in the past half hour)
[20:33] <nacc> yeah, i saw a bunch of php ones go through that were stalled for a while
[20:33] <nacc> so i'll stay patient :)
[20:38] <nacc> slangasek: and hey, a bunch of stuff just migrated :)
[21:01] <tjaalton> is there a way to make xorg-server trigger tests on the sphinx on proposed instead of bionic?
[21:02] -queuebot:#ubuntu-release- Unapproved: juju-core (xenial-proposed/main) [2.3.1-0ubuntu0.16.04.1 => 2.3.2-0ubuntu0.16.04.1] (ubuntu-server)
[21:07] <slangasek> tjaalton: yes; you can retrigger with all-proposed=1, or you can manually construct a trigger list that includes the sphinx in proposed
[21:08] <slangasek> using retry-autopkgtest-regressions
[21:09] <slangasek> which reminds me that no one has reviewed https://code.launchpad.net/~vorlon/ubuntu-archive-tools/fancier-autopkgtest-retries/+merge/335413 for me yet
[21:09] <slangasek> infinity, apw, sil2100: any of you want to review this in the next while, or shall I self-accept? ^^
[21:09] <tjaalton> so needs archive-admin powers to do that?
[21:10] <slangasek> tjaalton: not at all
[21:10] <slangasek> tjaalton: you need to be an ubuntu-dev, and use that script to trigger autopkgtests through the api
[21:10] <tjaalton> oh
[21:10] <tjaalton> ok
[21:11] <slangasek> tjaalton: where 'retry-autopkgtest-regressions --help' shows you that the interface to this api is horrible and involves launching web browsers from the commandline, but it's still an api ;)
[21:11] <tjaalton> hehe, sure thing, I'll have a look tomorrow so that xorg-server could hopefully finally migrate
[21:16] <slangasek> nacc: does anyone on server care about node?  new node-tap seems to be blocked by regressing its own tests on armhf
[21:32] <slangasek> tsimonq2: lubuntu cdimage includes updated
[21:35] <tsimonq2> slangasek: thank you
[21:38] <slangasek> http://releases.ubuntu.com/include/style.css - san-serif
[21:38] <slangasek> who's been putting serifs on my SAN
[21:42] -queuebot:#ubuntu-release- New source: golang-1.10-race-detector-runtime (bionic-proposed/primary) [0.0+svn285455-0ubuntu1]
[22:16] <flocculant> cyphermox slangasek - just rebooted machine, had some grub updates earlier - now seeing a weird text flashing issue
[22:16] <flocculant> bug 1748028 has a little screen capture of it attached
[22:38] -queuebot:#ubuntu-release- New: accepted golang-1.10-race-detector-runtime [source] (bionic-proposed) [0.0+svn285455-0ubuntu1]
[22:40] <nacc> slangasek: not that i know of
[22:41] -queuebot:#ubuntu-release- New binary: golang-1.10-race-detector-runtime [amd64] (bionic-proposed/universe) [0.0+svn285455-0ubuntu1] (no packageset)
[22:43] <doko> slangasek, tjaalton: the trigger would be python3.6 python3-stdlib-extensions python3-defaults. so maybe better all-proposed ...
[22:55] <doko> ginggs, slangasek: updated smokeqt (removing dangling symlinks causing perlqt ftbfs), and perlqt. I hope that doesn't break too many things, but updating smokeqt and not updating perlqt doesn't make sense
[22:57] -queuebot:#ubuntu-release- New: accepted golang-1.10-race-detector-runtime [amd64] (bionic-proposed) [0.0+svn285455-0ubuntu1]
[23:14] <slangasek> oops, let the ppc64el runners die again, bos02 is *also* missing base images for xenial on ppc64el :P
[23:15] <slangasek> (fixing again)
[23:15] -queuebot:#ubuntu-release- New binary: editorconfig-core-py [amd64] (bionic-proposed/universe) [0.12.1-1] (no packageset)
[23:15] -queuebot:#ubuntu-release- New binary: neuron [ppc64el] (bionic-proposed/universe) [7.5-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: neuron [amd64] (bionic-proposed/universe) [7.5-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: neuron [i386] (bionic-proposed/universe) [7.5-1] (no packageset)
[23:43] -queuebot:#ubuntu-release- New: accepted editorconfig-core-py [amd64] (bionic-proposed) [0.12.1-1]
[23:44] -queuebot:#ubuntu-release- New: accepted neuron [amd64] (bionic-proposed) [7.5-1]
[23:44] -queuebot:#ubuntu-release- New: accepted neuron [ppc64el] (bionic-proposed) [7.5-1]
[23:44] -queuebot:#ubuntu-release- New: accepted neuron [i386] (bionic-proposed) [7.5-1]
[23:45] -queuebot:#ubuntu-release- New: rejected gcc-8 [amd64] (bionic-proposed) [8-20180206-0ubuntu1]
[23:45] -queuebot:#ubuntu-release- New: rejected gcc-8 [armhf] (bionic-proposed) [8-20180206-0ubuntu1]
[23:45] -queuebot:#ubuntu-release- New: rejected gcc-8 [ppc64el] (bionic-proposed) [8-20180206-0ubuntu1]
[23:45] -queuebot:#ubuntu-release- New: rejected gcc-8 [arm64] (bionic-proposed) [8-20180207-1ubuntu1]
[23:45] -queuebot:#ubuntu-release- New: rejected gcc-8 [ppc64el] (bionic-proposed) [8-20180207-1ubuntu1]
[23:45] -queuebot:#ubuntu-release- New: rejected gcc-8 [arm64] (bionic-proposed) [8-20180206-0ubuntu1]
[23:45] -queuebot:#ubuntu-release- New: rejected gcc-8 [s390x] (bionic-proposed) [8-20180206-0ubuntu1]
[23:45] -queuebot:#ubuntu-release- New: rejected gcc-8 [s390x] (bionic-proposed) [8-20180207-1ubuntu1]
[23:45] -queuebot:#ubuntu-release- New: rejected gcc-8 [i386] (bionic-proposed) [8-20180206-0ubuntu1]
[23:45] -queuebot:#ubuntu-release- New: rejected gcc-8 [armhf] (bionic-proposed) [8-20180207-1ubuntu1]
[23:48] <doko> I don't get that one: https://launchpadlibrarian.net/356184332/buildlog_ubuntu-bionic-arm64.ruby-json_2.1.0+dfsg-1build1_BUILDING.txt.gz
[23:48] <doko> jruby -S rake clean
[23:48] <doko> rake aborted!
[23:48] <doko> Errno::EACCES: Permission denied - /usr/bin/make
[23:48] <doko> /<<BUILDDIR>>/ruby-json-2.1.0+dfsg/Rakefile:26:in `block in (root)'
[23:48] <doko> /<<BUILDDIR>>/ruby-json-2.1.0+dfsg/Rakefile:26:in `<main>'
[23:48] <doko> (See full trace by running task with --trace)
[23:50] <slangasek> doko: this happened in a 'clean' target; it's trying to remove /usr/bin/make?
[23:50] <slangasek> (speculating)
[23:51] <doko> it's arm64 only
[23:57] -queuebot:#ubuntu-release- Unapproved: accepted gnome-disk-utility [source] (artful-proposed) [3.26.1-0ubuntu1.1]