[05:17] <ginggs> would someone please RM old htseq binaries on armhf, i386 and s390x? it B-D on python-pysam which is not avaiable on those
[05:35] <doko> ginggs: hmm, they are not available?
[06:13] -queuebot:#ubuntu-release- Unapproved: ubuntu-report (bionic-proposed/main) [1.1.0 => 1.2.0~bionic] (no packageset)
[06:16] <ginggs> doko: so what blocks htseq then? according to update_excuses it is missing build on armhf, i386 and s390x
[06:26] <doko> ginggs: update_excuses only tells you about a missing build, not about the status of earlier uploads
[06:27] <doko> ahh, the -doc package ...
[06:29] -queuebot:#ubuntu-release- New: rejected qemu-ovmf-secureboot [source] (cosmic-proposed) [1.1.2-0ubuntu1]
[06:29] <doko> done
[06:29] <ginggs> doko:  thanks!
[06:32] <cpaelzer> where was that from?
[06:32] <cpaelzer> dannf was that you ^^?
[06:34] <doko> LocutusOfBorg: could you have a look at the python-mechanicalsoup autopkg tests? failing both in Debian and Ubuntu
[06:47] <LocutusOfBorg> doko, will try
[06:49] <LocutusOfBorg> can any AA please move linuxbrew-wrapper to multiverse?
[06:49] <LocutusOfBorg> aaand why didn't it end up in new queue like it did to Debian?
[06:49] <LocutusOfBorg> apw, "Move to contrib section. (Closes: #888957)"
[06:52] <LocutusOfBorg> cjwatson, aren't move to contrib important for us? I'm worried about how many undetected move we missed...
[06:52] <doko> LocutusOfBorg: might be as simple as mechanicalsoup.LinkNotFoundError -> mechanicalsoup.utils.LinkNotFoundError
[06:54] <LocutusOfBorg> doko, thanks! I'm already setting up the cosmic VM
[07:16] <ginggs> doko: btw, liggghts still shows up as a regression on armhf here https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#liggghts even though i think you removed the armhf binary, i'm not sure how to clear that
[07:30] <doko> ginggs: will it ftbfs when we rebuild? there is no other way to get rid off this record
[07:30] <doko> well, you could hint it
[07:32] <sil2100> Let me hint it in
[07:33] <ginggs> sil2100: thanks, and please  'force-badtest pyfai/0.15.0+dfsg1-1/amd64' ?  It passed once by accident on 2018-06-01  http://autopkgtest.ubuntu.com/packages/p/pyfai/cosmic/amd64
[07:34] <sil2100> ginggs: ACK
[07:34] <doko> ginggs: but this will show up again with the next version
[07:34] <ginggs> sil2100: I have some R hints that need their versions bumped too
[07:35] <doko> cpaelzer: could you (or server team) have a look at the failing autopkg tests triggered by postgresql-10 ?
[07:37] <sil2100> ginggs, doko: liggghts and pyfai have been badtested
[07:38] <sil2100> ginggs: which packages you need bumped?
[07:45] <ginggs> sil2100: looking...
 doko:  r-cran-rmarkdown/armhf and /s390x is due to missing haskell/pandoc
 doko:  r-cran-yaml/i386 is a regression due to new r-cran-yaml, r-cran-memoise is a alignment regression due to new r-cran-memoise - none are caused by the new r-base
[07:48] <ginggs> sil200: in hints-ubuntu - force-badtest r-bioc-annotationhub/2.10.1-1 r-bioc-annotationhub/2.12.0-2 r-bioc-annotationhub/2.12.0+dfsg-1
[07:49] <ginggs> sil2100: force-badtest r-bioc-biocparallel/1.14.1-1build1/s390x r-bioc-biocparallel/1.14.1-1build1/armhf
[07:51] <cpaelzer> doko: I was looking at PG-10 related tests already
[07:51] <cpaelzer> doko: one bug fixed, one block resolved by retries (flaky perl soemthing package) and two need a update for new versions in force-badtest
[07:51] <cpaelzer> the latter is in the review queue to infinity
[07:51] <ginggs> sil2100: i meant the above in hints-ubuntu/adconrad
[07:51] <cpaelzer> as his britney files had the old pglogical
[07:52] <doko> removed all old binaries in proposed, two weeks old ...
[07:53] <cpaelzer> doko: only libpqtypes is new to me, that was not there 3 days ago
[07:54] <cpaelzer> taking a look at that
[07:54] <doko> ginggs: htseq migrated
[07:54] <cpaelzer> doko: if you want to ack & push the britney hints please feel free https://code.launchpad.net/~paelzer/britney/hints-ubuntu-postgres-related-cosmic/+merge/348197 - otherwise I have to wait for infinity to get to it
[07:55] <ginggs> sil2100: and in hints-ubuntu/stefanor - force-badtest python-xarray/0.10.2-1/i386 python-xarray/0.10.7-1/i386
[07:55] <cpaelzer> will look at the new libpqtypes fail later today
[07:55] <ginggs> sil2100: and - force-badtest python-xarray/0.10.2-1/arm64 python-xarray/0.10.7-1/arm64
[07:56] <ginggs> sil2100: thanks in advance!
[07:59] <ginggs> doko: \o/ at least something could migrate!
[07:59] <sil2100> ginggs: I'll poke those in a moment
[08:00] <sil2100> yw!
[08:02] <doko> ginggs: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/ppc64el/s/sfepy/20180621_072525_11bac@/log.gz where does the gomp dependency come from? can't find it in mayavi2
[08:03] <doko> vtk6?
[08:03] <apw> LocutusOfBorg, linuxbrew-wrapper> looking
[08:06] <ginggs> doko: ENOCLUE- i wonder if building sfepy wth -O2 on ppc64el will help
[08:11] <sil2100> ginggs: ok, bumped
[08:12] <doko> sil2100: please could you update vorlon:force-badtest python-asdf/1.3.3-1/s390x to 2.0.1-1
[08:19] <cpaelzer> doko: the linpqtypes issues are resolved now
[08:19] <cpaelzer> doko: leaving only the mentioned MP to infinity open for pglogical to finally unblock it
[08:19] <cpaelzer> if you are allowed to do so, please ack and merge it
[08:20] <ginggs> sil2100: thanks, there's a typo in stefanor: force-badtest python-xarray/0.10.2-1/i386 python-xarray/0.10.2-1/i386  - the 2nd version should be  0.10.7-1
[08:29] <cjwatson> LocutusOfBorg: I'm sure we should have something to track that, yes.  The NEW queue is probably the wrong tool - it ends up there basically for circumstantial reasons in Debian (there's no way to do a component move AIUI, you have to remove and reupload)
[08:33] <LocutusOfBorg> yes cjwatson, it would be nice to do an archive sanity check for such mismatches
[08:34] <LocutusOfBorg> I remember having to bother for virtualbox-ext-pack, I limit the bothering to packages I moved, I don't check what other people do...
[08:34] <LocutusOfBorg> IANAL and I hate such things
[08:44] <doko> LocutusOfBorg: hmm, the mechanicalsoup fix was wrong
[08:47] <LocutusOfBorg> doko, yes, I'm debugging it right now
[08:47] <LocutusOfBorg> upstream has a commit too
[08:49] <sil2100> ginggs: whoops!
[08:52] <sil2100> doko: done
[08:52] <LocutusOfBorg> thanks apw
[09:05] -queuebot:#ubuntu-release- Unapproved: accepted gdm3 [source] (bionic-proposed) [3.28.2-0ubuntu1.3]
[09:07] <ginggs> sil2100: did you see the r-cran-rmarkdown etc, hints doko quoted me on above?
[09:08] <ginggs> sil2100: force-badtest r-cran-rmarkdown/1.10+dfsg-1/armhf  r-cran-rmarkdown/1.10+dfsg-1/s390x
[09:09] <ginggs> sil2100: force-badtest r-cran-yaml/2.1.19-1ubuntu1/i386
[09:09] <ginggs> sil2100: force-badtest r-cran-memoise/1.1.0-2/armhf
[09:10] <ginggs> and I think r-base will be ready to migrate after that!
[09:15] <sil2100> I think I missed those, but I just took a look at those and will be pushing hints
[09:15] <sil2100> Since they seem to be valid badtests
[09:17] <sil2100> ginggs: should be done
[09:17] <ginggs> sil2100: thanks again!
[09:17] <sil2100> yw!
[09:17]  * sil2100 goes back to his SRUs
[09:32] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox [source] (bionic-proposed) [5.2.10-dfsg-6ubuntu18.04.1]
[09:33] -queuebot:#ubuntu-release- Unapproved: rejected snapd-glib [source] (bionic-proposed) [1.40-0ubuntu0.18.04.1]
[09:41] -queuebot:#ubuntu-release- Unapproved: accepted zlib [source] (trusty-proposed) [1:1.2.8.dfsg-1ubuntu1.1]
[09:55] -queuebot:#ubuntu-release- Unapproved: accepted nbd [source] (bionic-proposed) [1:3.16.2-1ubuntu0.1]
[11:04] <doko> ginggs: it's entangled with python-numpy
[11:04] <doko> and  r-bioc-delayedarray/0.6.0+dfsg-1: armhf
[11:07] <ginggs> doko: r-bioc-delayedarray/0.6.1+dfsg-1 passes
[11:07] <ginggs> doko: but yeah, numpy :( sandro should have uploaded to experimental and given rdeps a chance to catch up
[11:12] <doko> ginggs: we could "resolve" this dependency by removing r-cran-fastcluster and r-bioc-cummerbund from the release pocket
[11:13] <ginggs> doko: no objections
[11:14] <doko> did you give back the r-bioc-delayedarray tests?
[11:15] -queuebot:#ubuntu-release- New binary: ros-class-loader [amd64] (cosmic-proposed/universe) [0.4.1-2] (no packageset)
[11:15] <ginggs> doko: locutus did retry-autopkgtest-regressions a little while ago, looks all green to me
[11:16] -queuebot:#ubuntu-release- New binary: ros-class-loader [i386] (cosmic-proposed/universe) [0.4.1-2] (no packageset)
[11:16] <doko> ahh, didn't reload
[11:17] -queuebot:#ubuntu-release- New binary: ros-class-loader [ppc64el] (cosmic-proposed/universe) [0.4.1-2] (no packageset)
[11:19] -queuebot:#ubuntu-release- New binary: ros-class-loader [s390x] (cosmic-proposed/universe) [0.4.1-2] (no packageset)
[11:25] -queuebot:#ubuntu-release- New binary: ros-class-loader [arm64] (cosmic-proposed/universe) [0.4.1-2] (no packageset)
[11:25] -queuebot:#ubuntu-release- New binary: ros-class-loader [armhf] (cosmic-proposed/universe) [0.4.1-2] (no packageset)
[11:26] <apw> ginggs, looks like there are still two laggers for r-base to migrate
[11:26] <doko> apw: which ones?
[11:27] <apw> r-cran-metamix, r-cran-rmpi
[11:28] <apw> though the first of those is new, so i don't see how that is uninstallable
[11:30] <doko> rmpi is entabled with openmpi :-/
[11:30] <apw> bugger
[11:30] <doko> and openmpi with python-numpy
[11:31] <doko> ok, removing rmpi as well from the release pocket. leaf package as well
[13:23] <apw> doko, something's testing regressed for r-base (r-other-mott-happy) pulling it back from Valid candiate
[13:24] <doko> ginggs: ^^^
[13:26] <apw> ginggs, if i am reading this log right, this packages doesn't depend on R but uses it
[13:31] <doko> and more autopkg test regressions
[13:49] <ginggs> looks like r-other-mott-happy passed its tests for the first time ever, so makes previous 'always failed' results invalid
[14:05] <apw> ginggs, and yet, from the log that looks to be completely impossible
[14:05] -queuebot:#ubuntu-release- Unapproved: linux (xenial-updates/main) [4.4.0-130.156 => 4.4.0-130.156] (core, kernel) (sync)
[14:09] <ginggs> apw: it seems it was 'always-failed' because it didn't have any tests, now Testsuite: autopkgtest-pkg-r in debian/control has kicked in
[14:09] <ginggs> https://ci.debian.net/packages/r/r-other-mott-happy/unstable/amd64/
[14:09] <apw> trying to work out how it ever passed
[14:11] <ginggs> apw it didn't http://autopkgtest.ubuntu.com/packages/r-other-mott-happy/bionic/amd64
[14:12] <apw> http://autopkgtest.ubuntu.com/packages/r-other-mott-happy/cosmic/amd64
[14:12] <apw> ginggs, ^ yes it idid
[14:13] <ginggs> it did now - but didn't ever work in the past
[14:15] -queuebot:#ubuntu-release- Unapproved: rejected linux [sync] (xenial-updates) [4.4.0-130.156]
[14:19] <apw> ginggs, they do look to be a noop of a test though
[14:20] <apw> ginggs, though does that not also say that LocutusOfBorg got it to run since
[14:21] <apw> so that is confusing ...
[14:23] <ginggs> apw: 2.4-2 always fails - 2.4-3 passes - look carefully in the logs of the 11:47, 11:51 and 11:52 tests
[14:24] <ginggs> Get:1 http://ftpmaster.internal/ubuntu cosmic/universe amd64 r-other-mott-happy.hbrem amd64 2.4-2 [137 kB]
[14:25] <ginggs> whereas the passing test has Get:44 http://ftpmaster.internal/ubuntu cosmic-proposed/universe amd64 r-other-mott-happy.hbrem amd64 2.4-3 [214 kB]
[14:25] -queuebot:#ubuntu-release- Unapproved: broadcom-sta (xenial-proposed/multiverse) [6.30.223.271-3~16.04.2 => 6.30.223.271-3~16.04.3] (no packageset)
[14:27] <ginggs> it often happens that the test suite runs against a different version of the package
[14:27] <apw> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/r/r-other-mott-happy/20180621_114749_38f60@/log.gz
[14:27] <apw> doesn't that log say -3 though, and is a fial ?
[14:29] <ginggs> Get:1 http://ftpmaster.internal/ubuntu cosmic-proposed/universe r-other-mott-happy 2.4-3 (dsc) [2161 B]
[14:29] <ginggs> Get:1 http://ftpmaster.internal/ubuntu cosmic/universe amd64 r-other-mott-happy.hbrem amd64 2.4-2 [137 kB]
[14:29] <apw> oh that is utterly useless
[14:32] <apw> ginggs, so for that one we might well want to test it against itself again, then it will test -3 right ?
[14:32] <apw> ginggs, and r-base at the same time, ugg
[14:34] <ginggs> apw the trigger is r-other-mott-happy/2.4-3 it should pull in r-base/3.5.0-5 because R packages at least have a dependency on it
[14:34] <ginggs> ^ if the trigger is...
[14:56] -queuebot:#ubuntu-release- Unapproved: dm-writeboost (xenial-proposed/universe) [2.2.6-1~16.04.2 => 2.2.6-1~16.04.3] (no packageset)
[15:09] -queuebot:#ubuntu-release- Unapproved: bcmwl (xenial-proposed/restricted) [6.30.223.271+bdcom-0ubuntu1~1.2 => 6.30.223.271+bdcom-0ubuntu1~1.3] (kubuntu, ubuntu-desktop)
[15:45] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.33 => 2.33.1] (desktop-core, ubuntu-server)
[15:49] -queuebot:#ubuntu-release- Unapproved: snapd (artful-proposed/main) [2.33+17.10 => 2.33.1+17.10] (desktop-core, ubuntu-server)
[15:49] -queuebot:#ubuntu-release- Unapproved: snapd (bionic-proposed/main) [2.33+18.04 => 2.33.1+18.04] (desktop-core, ubuntu-server)
[15:51] -queuebot:#ubuntu-release- Unapproved: snapd (trusty-proposed/universe) [2.33~14.04 => 2.33.1~14.04] (no packageset)
[15:54] <dannf> cpaelzer:  qemu-ovmf-secureboot ? no idea what that is
[16:02] <ginggs>     * amd64: r-cran-metamix, r-cran-rmpi - why are these still a problem?
[16:08] <kenvandine> can someone please reject flatpak from the bionic-proposed queue?
[16:09] <apw> kenvandine, can do, why so
[16:09] <kenvandine> we are going to skip straight to 1.0
[16:10] <kenvandine> they are preparing a 1.0 release now
[16:10] <apw> ack
[16:10] <kenvandine> apw, thx!
[16:11] -queuebot:#ubuntu-release- Unapproved: rejected flatpak [source] (bionic-proposed) [0.11.8.3-0ubuntu0.1]
[16:13] <apw> kenvandine, ^
[16:13] <kenvandine> apw, thanks!
[16:25] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (bionic-proposed) [2.33.1+18.04]
[16:26] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (artful-proposed) [2.33.1+17.10]
[16:27] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.33.1]
[16:27] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (trusty-proposed) [2.33.1~14.04]
[16:35] <LocutusOfBorg>     * amd64: r-cran-metamix, r-cran-rmpi
[16:35] <LocutusOfBorg>     * arm64: r-cran-metamix, r-cran-rmpi
[16:35] <LocutusOfBorg> why are them still blocking britney and r-base to migrate?
[16:35] <LocutusOfBorg> doko, apw ^^^ pleeeeeeeease
[16:35] <LocutusOfBorg> new run is ongoing...
[16:35] <LocutusOfBorg> (I mean auto-sync run)
[16:36] <LocutusOfBorg> they are moved in proposed
[16:36] <LocutusOfBorg> maybe a no.change rebuild might fix?
[16:45] <teward> they don't depend on perl at all do they?  i only ask since the perl migration is holding up several of the things I've pushed into the repos too :P
[16:52] <doko> LocutusOfBorg: they should not block. removed from the release pocket
[16:53] <teward> just to check in, what is the current status of the perl migration?  is it still 'in progress'?  (the system keeps yelling about nginx being stuck in proposed for > 30 days to me, and I'm curious what the progress is, if any)
[16:53] <doko> teward: if nobody is working on it, I would hardly call it as "in progress"
[16:54] <teward> doko: well I can't tell is the thing
[16:54] <teward> for all intents and purposes it *should* have migrated if autopkgtests are the only thing holding it back
[16:55] <teward> but since update excuses still shows it as 'valid candidate' for perl and nginx, and nginx is held because Perl hasn't migrated yet, it tends to make me head-scratch as to "What the heck is going on"
[16:56] <teward> and the latest Perl has been in the proposed for 11 days, and still says "Valid Candidate"
[16:56] <teward> so, again, I ask if there's some ongoing migration that's not listed somewhere that's preventing it from automatically migrating.  last time about a month ago there was, but i haven't heard anything since
[16:56] <teward> except for the archive system complaining about nginx being stuck in proposed for 30+ days
[16:58] -queuebot:#ubuntu-release- New: accepted ros-class-loader [amd64] (cosmic-proposed) [0.4.1-2]
[16:58] -queuebot:#ubuntu-release- New: accepted ros-class-loader [armhf] (cosmic-proposed) [0.4.1-2]
[16:58] -queuebot:#ubuntu-release- New: accepted ros-class-loader [ppc64el] (cosmic-proposed) [0.4.1-2]
[16:58] -queuebot:#ubuntu-release- New: accepted ros-class-loader [arm64] (cosmic-proposed) [0.4.1-2]
[16:58] -queuebot:#ubuntu-release- New: accepted ros-class-loader [s390x] (cosmic-proposed) [0.4.1-2]
[16:58] -queuebot:#ubuntu-release- New: accepted ros-class-loader [i386] (cosmic-proposed) [0.4.1-2]
[16:59] <doko> it has been there for much longer
[17:00] <teward> yes, it has.  at least a month or more, because NGINX is blocked by it
[17:01] <teward> which brings me back to my original question: "What's up with Perl?"
[17:01] <teward> if the answer is "Nobody Knows" then my next question is "Who should I be prodding next to ask?"
[17:19] <cjwatson> I just added a gdal 2.3.0 transition tracker, since that seems at least implicated.  Should show up in a bit
[17:51] <cpaelzer> dannf: I found who did it, it was cyphermox
[18:20] <cyphermox> dannf: I'm trying to set something up so that we can ship firmware with preloaded Microsoft certs for people to use Secure Boot from the start
[19:00] -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (xenial-proposed/universe) [4.13.0-1031.35] (kernel)
[19:15] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (xenial-proposed) [4.13.0-1031.35]
[19:19] <apw> cjwatson, and i think that gdal transition tracker says that the last thing is broken because pandoc is broken
[19:20] <LocutusOfBorg> doko, I know what britney says but britney says also otherwise     * arm64: r-cran-metamix, r-cran-pbivnorm, r-cran-rmpi
[19:27] -queuebot:#ubuntu-release- Unapproved: accepted dovecot [source] (bionic-proposed) [1:2.2.33.2-1ubuntu4.1]
[19:29] <doko> cjwatson: this is just osmcoastline, which is blocked on pandoc
[19:30] <apw> which is blocked because haskell is deeply unhappy for armhf
[19:31] <apw> haskell-cryptonite seems to have test-suite failures
[19:34] <LocutusOfBorg> I might think wrt disabling testsuite on armhf for aes, and see how much it progresses
[19:34] <LocutusOfBorg> this is a problem in Debian too BTW
[19:34] <LocutusOfBorg> other things are mostly clear
[19:35] <LocutusOfBorg> (pandoc is still a big problem btw)
[19:35] -queuebot:#ubuntu-release- Unapproved: accepted snapd-glib [source] (bionic-proposed) [1.41-0ubuntu0.18.04.1]
[19:49] -queuebot:#ubuntu-release- Unapproved: accepted networkd-dispatcher [source] (bionic-proposed) [1.7-0ubuntu3.2]
[20:01] -queuebot:#ubuntu-release- Unapproved: accepted unattended-upgrades [source] (bionic-proposed) [1.1ubuntu1.18.04.1]
[20:05] <doko> the s390x issue is a different one, a big-endian problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897001
[20:16] <bdmurray> apw: Could you look at bug 1777646 for me? I'm confused as the description mentions 4.13 but the debdiff is for 4.14.
[20:20] <apw> bdmurray, ok so the fix is to make bcwml support v4.14 and v4.15 kernels; the testing is against 4.4, 4.13, and 4.15 whihc are the various kernels that were avilable at the time, and all of which it must work with
[20:21] <apw> bdmurray, this is part of preparing for linux-hwe to move to v4.15 for the point release
[20:22] <bdmurray> apw: but there is not fix for 4.13 afaict
[20:22] <bdmurray> s/not/no/
[20:31] -queuebot:#ubuntu-release- Unapproved: rejected unattended-upgrades [source] (artful-proposed) [1.2ubuntu1~17.10.0]
[20:45] <apw> bdmurray, right, it should already work for v4.13, just testing there to confirm it is not regressed
[20:50] <doko> LocutusOfBorg: looking at update_output, I don't see this line anymore. but the list of uninstallable packages includes a lot of openmpi related things.
[21:07] <LocutusOfBorg> doko, there is an hint with just
[21:07] <LocutusOfBorg>     * amd64: r-cran-metamix, r-cran-rmpi
[21:07] <LocutusOfBorg> left
[21:44] <ginggs> doko, LocutusOfBorg: i think r-base migrated
[21:47] <slangasek> tada
[21:48] <ginggs> what was blocking it?
[21:48] <slangasek> ginggs: the autohinter was being too greedy and including some packages that were instantly uninstallable
[21:50] <ginggs> slangasek: ah ok, thanks! so did you have to manually hint it?
[21:50] <slangasek> ginggs: yep
[22:51] -queuebot:#ubuntu-release- Unapproved: python3-defaults (bionic-proposed/main) [3.6.5-3 => 3.6.5-3ubuntu1] (core)
[23:00] -queuebot:#ubuntu-release- Unapproved: python3-defaults (artful-proposed/main) [3.6.3-0ubuntu2 => 3.6.3-0ubuntu3] (core)
[23:29] -queuebot:#ubuntu-release- New binary: sfcgal [s390x] (cosmic-proposed/universe) [1.3.5-2] (no packageset)
[23:38] -queuebot:#ubuntu-release- New binary: sfcgal [ppc64el] (cosmic-proposed/universe) [1.3.5-2] (no packageset)
[23:39] -queuebot:#ubuntu-release- New binary: sfcgal [i386] (cosmic-proposed/universe) [1.3.5-2] (no packageset)