User1: I noticed something was FTBFS on -proposed pocket because of missing cmake (probably uninstallable)
User1: I'm retrying something, now that haskell is gone
User1: also, there was stuff stuck since months on proposed, with fixes in debian unstable, I syncd it
-queuebot:#ubuntu-release- New binary: quickfix [s390x] (eoan-proposed/universe) [1.15.1+dfsg-2] (no packageset)
-queuebot:#ubuntu-release- New binary: taffybar [amd64] (eoan-proposed/none) [3.0.0-2] (no packageset)
User1: (the total queue size shouldn't change, because it was already there)
-queuebot:#ubuntu-release- New binary: quickfix [amd64] (eoan-proposed/universe) [1.15.1+dfsg-2] (no packageset)
-queuebot:#ubuntu-release- New binary: quickfix [i386] (eoan-proposed/universe) [1.15.1+dfsg-2] (no packageset)
-queuebot:#ubuntu-release- New binary: taffybar [i386] (eoan-proposed/none) [3.0.0-2] (no packageset)
-queuebot:#ubuntu-release- New binary: quickfix [ppc64el] (eoan-proposed/universe) [1.15.1+dfsg-2] (no packageset)
User1: e.g. taffybar has been removed few days ago because of haskell ^^ its just a fixed comeback
-queuebot:#ubuntu-release- New binary: taffybar [s390x] (eoan-proposed/none) [3.0.0-2] (no packageset)
User1: quickfix was FTBFS on i386 due to glibc/new gcc with test failures, but the library looks like not used in the archive, probably just internal
User1: snakemake was not even installable because of python crash during apt
User1: so all reverse-deps (e.g. embree were FTBFS because of it)
User1: and so on
-queuebot:#ubuntu-release- New binary: quickfix [arm64] (eoan-proposed/universe) [1.15.1+dfsg-2] (no packageset)
-queuebot:#ubuntu-release- New binary: quickfix [armhf] (eoan-proposed/universe) [1.15.1+dfsg-2] (no packageset)
-queuebot:#ubuntu-release- New binary: taffybar [arm64] (eoan-proposed/universe) [3.0.0-2] (no packageset)
-queuebot:#ubuntu-release- New binary: taffybar [armhf] (eoan-proposed/universe) [3.0.0-2] (no packageset)
User2: xfce4-sntray-plugin because it's got a very low popcon, leaf package, and fixes ftbfs with the version of vala-panel that's in eoan.
-queuebot:#ubuntu-release- New binary: igdiscover [amd64] (eoan-proposed/universe) [0.11-3] (no packageset)
-queuebot:#ubuntu-release- Unapproved: snapd (bionic-proposed/main) [2.40+18.04 => 2.41+18.04] (desktop-core, ubuntu-server)
-queuebot:#ubuntu-release- Unapproved: snapd (disco-proposed/main) [2.40+19.04 => 2.41+19.04] (core)
-queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.40 => 2.41] (desktop-core, ubuntu-server)
User1: igdiscover was the one failing to install its build-dependencies because of SyntaxError: duplicate argument 'stay_on_remote' in function definition (src:snakemake)
User1: any AA please? https://bugs.launchpad.net/ubuntu/+source/samtools/+bug/1843387
User3: Launchpad bug 1843387 in samtools (Ubuntu) "samtools: please remove i386 binary, already gone in Debian" [Undecided,New]
User4: some problem with request.cgi giving false errors atm
User4: it's being looked into
-queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (bionic-proposed/main) [4.15.0-1042.45] (kernel)
User5: request.cgi should be working again. We started calling flask.escape on all inputs, but accidentally on None and flask.escape(None) = Markup("None"), which was not None.
-queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (bionic-proposed) [4.15.0-1042.45]
-queuebot:#ubuntu-release- New: accepted igdiscover [amd64] (eoan-proposed) [0.11-3]
-queuebot:#ubuntu-release- New: accepted quickfix [arm64] (eoan-proposed) [1.15.1+dfsg-2]
-queuebot:#ubuntu-release- New: accepted quickfix [i386] (eoan-proposed) [1.15.1+dfsg-2]
-queuebot:#ubuntu-release- New: accepted quickfix [s390x] (eoan-proposed) [1.15.1+dfsg-2]
-queuebot:#ubuntu-release- New: accepted taffybar [arm64] (eoan-proposed) [3.0.0-2]
-queuebot:#ubuntu-release- New: accepted taffybar [i386] (eoan-proposed) [3.0.0-2]
-queuebot:#ubuntu-release- New: accepted quickfix [amd64] (eoan-proposed) [1.15.1+dfsg-2]
-queuebot:#ubuntu-release- New: accepted quickfix [ppc64el] (eoan-proposed) [1.15.1+dfsg-2]
-queuebot:#ubuntu-release- New: accepted taffybar [armhf] (eoan-proposed) [3.0.0-2]
-queuebot:#ubuntu-release- New: accepted quickfix [armhf] (eoan-proposed) [1.15.1+dfsg-2]
-queuebot:#ubuntu-release- New: accepted taffybar [s390x] (eoan-proposed) [3.0.0-2]
-queuebot:#ubuntu-release- New: accepted taffybar [amd64] (eoan-proposed) [3.0.0-2]
User5: User4 ok, more work needed, as flask.escape() first calls str() or something
User5: User4 So doing except .. as e: invalid(e) fails right now
User4: which case is that?
User5: I'll just call str() in invalid I guess
User4: invalid release or something?
User4: yes
User5: User4 All the checking raises ValueError which we catch and call invalid()
User4: right
User4: I guess either stringify in there or always pass invalid() a string
User5: User4 should be fixed now, same branch as before
User5: User4 I call str() in invalid(), as that's how you'd expect it to work
User5: I mean, you can print() an exception, you should be able to pass it to invalid() to
User5: *too
User4: makes sense
User5: ValueError: Unknown release eofejifejoan
User5: love that
User4: did you want to reply to the original bug btw?
User4: say that the subsequent problem got fixed
User5: oh yeah
User4: then he can come back with the next instance of it :>
User6: vorlon, User7 did you find out what happens with the generated of component mismatches? again out of date
User7: I wasn't looking at this
User5: If anyone sees any more errors from request.cgi, please ping me!
User5: I'll be checking in with error.log from time to time
User5: but not _that_ often
User7: Sometimes I have stuff to say about why some bit of the archive-reports infra is the way it is, but in general I can't be on the hook for operating it any more
User4: don't see any hung processes
User4: archive-reports is doing an auto-sync dry run at the minute, but hasn't been running very long
-queuebot:#ubuntu-release- New binary: rust-ansi-term [armhf] (eoan-proposed/universe) [0.12.0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-ansi-term [s390x] (eoan-proposed/universe) [0.12.0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-ansi-term [i386] (eoan-proposed/universe) [0.12.0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-ansi-term [amd64] (eoan-proposed/universe) [0.12.0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-indexmap [amd64] (eoan-proposed/universe) [1.1.0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-ansi-term [arm64] (eoan-proposed/universe) [0.12.0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-indexmap [i386] (eoan-proposed/universe) [1.1.0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-ansi-term [ppc64el] (eoan-proposed/universe) [0.12.0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-indexmap [s390x] (eoan-proposed/universe) [1.1.0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-indexmap [arm64] (eoan-proposed/universe) [1.1.0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-rand-xoshiro [amd64] (eoan-proposed/universe) [0.3.1-2] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-indexmap [armhf] (eoan-proposed/universe) [1.1.0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-rand-xoshiro [i386] (eoan-proposed/universe) [0.3.1-2] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-rand-xoshiro [s390x] (eoan-proposed/universe) [0.3.1-2] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-subtle [i386] (eoan-proposed/universe) [2.1.1-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-subtle [amd64] (eoan-proposed/universe) [2.1.1-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-subtle [s390x] (eoan-proposed/universe) [2.1.1-1] (no packageset)
User1: I'm trying to cleanup the rust proposed packages...
-queuebot:#ubuntu-release- New binary: rust-rand-xoshiro [arm64] (eoan-proposed/universe) [0.3.1-2] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-rand-xoshiro [armhf] (eoan-proposed/universe) [0.3.1-2] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-indexmap [ppc64el] (eoan-proposed/universe) [1.1.0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-subtle [armhf] (eoan-proposed/universe) [2.1.1-1] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-subtle [arm64] (eoan-proposed/universe) [2.1.1-1] (no packageset)
-queuebot:#ubuntu-release- New: accepted rust-ansi-term [amd64] (eoan-proposed) [0.12.0-1]
-queuebot:#ubuntu-release- New: accepted rust-ansi-term [armhf] (eoan-proposed) [0.12.0-1]
-queuebot:#ubuntu-release- New: accepted rust-ansi-term [ppc64el] (eoan-proposed) [0.12.0-1]
-queuebot:#ubuntu-release- New: accepted rust-indexmap [amd64] (eoan-proposed) [1.1.0-1]
-queuebot:#ubuntu-release- New: accepted rust-indexmap [armhf] (eoan-proposed) [1.1.0-1]
-queuebot:#ubuntu-release- New: accepted rust-indexmap [ppc64el] (eoan-proposed) [1.1.0-1]
-queuebot:#ubuntu-release- New: accepted rust-ansi-term [arm64] (eoan-proposed) [0.12.0-1]
-queuebot:#ubuntu-release- New: accepted rust-ansi-term [s390x] (eoan-proposed) [0.12.0-1]
-queuebot:#ubuntu-release- New: accepted rust-indexmap [i386] (eoan-proposed) [1.1.0-1]
-queuebot:#ubuntu-release- New: accepted rust-ansi-term [i386] (eoan-proposed) [0.12.0-1]
-queuebot:#ubuntu-release- New: accepted rust-indexmap [s390x] (eoan-proposed) [1.1.0-1]
-queuebot:#ubuntu-release- New: accepted rust-indexmap [arm64] (eoan-proposed) [1.1.0-1]
-queuebot:#ubuntu-release- New binary: rust-rand-xoshiro [ppc64el] (eoan-proposed/universe) [0.3.1-2] (no packageset)
-queuebot:#ubuntu-release- New binary: rust-subtle [ppc64el] (eoan-proposed/universe) [2.1.1-1] (no packageset)
User1: please NBS cleanup libquickfix16 :)
-queuebot:#ubuntu-release- New: accepted rust-rand-xoshiro [amd64] (eoan-proposed) [0.3.1-2]
-queuebot:#ubuntu-release- New: accepted rust-rand-xoshiro [armhf] (eoan-proposed) [0.3.1-2]
-queuebot:#ubuntu-release- New: accepted rust-rand-xoshiro [ppc64el] (eoan-proposed) [0.3.1-2]
-queuebot:#ubuntu-release- New: accepted rust-subtle [amd64] (eoan-proposed) [2.1.1-1]
-queuebot:#ubuntu-release- New: accepted rust-subtle [armhf] (eoan-proposed) [2.1.1-1]
-queuebot:#ubuntu-release- New: accepted rust-subtle [ppc64el] (eoan-proposed) [2.1.1-1]
-queuebot:#ubuntu-release- New: accepted rust-rand-xoshiro [arm64] (eoan-proposed) [0.3.1-2]
-queuebot:#ubuntu-release- New: accepted rust-rand-xoshiro [s390x] (eoan-proposed) [0.3.1-2]
-queuebot:#ubuntu-release- New: accepted rust-subtle [i386] (eoan-proposed) [2.1.1-1]
-queuebot:#ubuntu-release- New: accepted rust-rand-xoshiro [i386] (eoan-proposed) [0.3.1-2]
-queuebot:#ubuntu-release- New: accepted rust-subtle [s390x] (eoan-proposed) [2.1.1-1]
-queuebot:#ubuntu-release- New: accepted rust-subtle [arm64] (eoan-proposed) [2.1.1-1]
User7: User1 done
User1: ta
-queuebot:#ubuntu-release- New binary: linux-signed [s390x] (eoan-proposed/main) [5.3.0-10.11] (core, kernel)
-queuebot:#ubuntu-release- New binary: linux-signed [amd64] (eoan-proposed/main) [5.3.0-10.11] (core, kernel)
-queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (eoan-proposed/main) [5.3.0-10.11] (core, kernel)
-queuebot:#ubuntu-release- New binary: linux-signed [arm64] (eoan-proposed/main) [5.3.0-10.11] (core, kernel)
-queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (eoan-proposed) [5.3.0-10.11]
-queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (eoan-proposed) [5.3.0-10.11]
-queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (eoan-proposed) [5.3.0-10.11]
-queuebot:#ubuntu-release- New: accepted linux-signed [s390x] (eoan-proposed) [5.3.0-10.11]
User8: lvm2 tries to confuse me, it now has Recommends: thin-provisioning-tools whcih shoudl trigger MIR in bug 1828887
User3: bug 1828887 in thin-provisioning-tools (Ubuntu) "[MIR] thin-provisioning-tools" [Undecided,In progress] https://launchpad.net/bugs/1828887
User8: but it went straight to -release - what am I missing?
-queuebot:#ubuntu-release- New binary: printrun [amd64] (eoan-proposed/universe) [2.0.0~rc5-1] (no packageset)
User8: User6 User9 is one of you around atm to take an AAs look at this?
-queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (bionic-proposed/partner) [1:20190813.1-0ubuntu91.69.162.6 => 1:20190910.1-0ubuntu91.69.162.6] (no packageset)
-queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (xenial-proposed/partner) [1:20190813.1-0ubuntu91.69.162.6 => 1:20190910.1-0ubuntu91.69.162.6] (no packageset)
-queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (disco-proposed/partner) [1:20190813.1-0ubuntu91.69.162.6 => 1:20190910.1-0ubuntu91.69.162.6] (no packageset)
User9: cpaelzer, i am not sure that component missmatches is a blocker to promotion; to release of eoan yes
User9: cpaelzer, also the reports which should be whining about it, are not
User8: yeah I haven't seen it in https://people.canonical.com/~ubuntu-archive/component-mismatches
User10: I also have a component mismatch question, about https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#php-defaults
User10: I think those php7.3 packages should be in main, like their php7.2 counterparts are (and 7.2 will soon be dropped)
User9: those reports all last updated around 3am utc so ... that sounds broken
User8: oh that is am
User8: I silently expected 4pm +2H TZ offset
-queuebot:#ubuntu-release- New binary: printrun [s390x] (eoan-proposed/universe) [2.0.0~rc5-1ubuntu1] (no packageset)
User8: I'm unsure what to do now, I have an approved MIR and a package in main with a dependency
User9: cpaelzer, it has no am/pm suffix so it is '24 hour clock' or 'military time'
User8: but this outdated report might be related
-queuebot:#ubuntu-release- New binary: printrun [amd64] (eoan-proposed/universe) [2.0.0~rc5-1ubuntu1] (no packageset)
-queuebot:#ubuntu-release- New binary: printrun [i386] (eoan-proposed/universe) [2.0.0~rc5-1ubuntu1] (no packageset)
User8: my upload just is an hour old (or two)
-queuebot:#ubuntu-release- New binary: printrun [arm64] (eoan-proposed/universe) [2.0.0~rc5-1ubuntu1] (no packageset)
User9: cpaelzer, i don't think you need to do anything, if it has an approved MIR, then we would find out that at the same time we find out there is a missmatch
User8: well, I'd want to see the actual promotion of the packages happen to feel like I can forget about it
User8: but I'm fine waiting another day
-queuebot:#ubuntu-release- New binary: printrun [armhf] (eoan-proposed/universe) [2.0.0~rc5-1ubuntu1] (no packageset)
User8: and see if reports recover
-queuebot:#ubuntu-release- New binary: printrun [ppc64el] (eoan-proposed/universe) [2.0.0~rc5-1ubuntu1] (no packageset)
User8: User10 I'll stop talking and leave this space for you and your php-defaults question
-queuebot:#ubuntu-release- New: accepted printrun [amd64] (eoan-proposed) [2.0.0~rc5-1]
-queuebot:#ubuntu-release- New: accepted printrun [amd64] (eoan-proposed) [2.0.0~rc5-1ubuntu1]
-queuebot:#ubuntu-release- New: accepted printrun [armhf] (eoan-proposed) [2.0.0~rc5-1ubuntu1]
-queuebot:#ubuntu-release- New: accepted printrun [ppc64el] (eoan-proposed) [2.0.0~rc5-1ubuntu1]
-queuebot:#ubuntu-release- New: accepted printrun [arm64] (eoan-proposed) [2.0.0~rc5-1ubuntu1]
-queuebot:#ubuntu-release- New: accepted printrun [s390x] (eoan-proposed) [2.0.0~rc5-1ubuntu1]
-queuebot:#ubuntu-release- New: accepted printrun [i386] (eoan-proposed) [2.0.0~rc5-1ubuntu1]
User10: ok, https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed is the correct report, and it suggest moving these php7.3 packages to main
User1: thanks to whoever accepted printrun, this will make finally cairosvg migrate!
User1: vorlon, FYI, I'm syncing rust-rand, because according to https://github.com/rust-lang/rust/issues/58516 it is "fixed" (workaround) in wasm-bindgen
User11: rust-lang issue 58516 in rust "LLVM ERROR: Undefined temporary symbol when compiling wasm-bindgen-macro-support on powerpc64+powerpc64le linux" [A-Llvm, C-Bug, O-Powerpc, T-Compiler, Open]
User7: printrun> YW
-queuebot:#ubuntu-release- New sync: rust-c2-chacha (eoan-proposed/primary) [0.2.2-1]
User4: I'll take a look at component-mismatches now
User1: btw, I would appreciate an AA helping me understand what is blocking antlr
User1: for some reasons now update_output is clear
User1: got it
User1: I just uploaded ghc 8.8.1 to Debian experimental, can you *please* blacklist haskell to avoid people being sad?
User9: ba
User9: ahasenack, i thought that sounded familiar, the whole thing was in main the other week and i pulled back the ones in 7.2 which were in universe ... and now they are all in universe again, sigh
User12: No these are src:php-defaults this time I think?
User10: src:php-default builds, say, php-dev, which pulls in php7.3-dev
User10: last time it was from src:php7.3. For example, bin:php7.3-imap comes from src:php7.3-imap, but is pulled in by bin:php-imap, which comes from src:php-defaults
User10: phew
User10: so php-imap is in universe (correct), php7.3-imap is also in universe (correct)
User12: It isn't stuck on php-imap though?
User12: php-ldap is in main (wrong I think) but php7.3-ldap is in universe (correct I think)
User7: User1 there'll be no auto-syncs until after eoan releases, and certainly not from experimental.  I don't see why this is urgent
User10: User12 I just used php-imap as an example of what apw fixed a week or two ago
User10: User12 he said "that sounded familiar"
User12: Ah
User1: cjwatson, I want to avoid manual errors :)
User1: and more important, myself forgetting to ask it
User1: :)
User13: User6 previously component-mismatches was not running due to a stale lockfile (with a timestamp in July!) causing a failure at an earlier stage of the archive-reports run.  That stamp file is not there now, so if the c-m report isn't being run, someone will have to dig through it again to see what's failing, given that there's no real error output from archive-reports
User13: User1 how does rust-wasm-bindgen being fixed justify syncing a new upstream version of rust-rand?
-queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (bionic-proposed) [1:20190910.1-0ubuntu91.69.162.6]
-queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (disco-proposed) [1:20190910.1-0ubuntu91.69.162.6]
-queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (xenial-proposed) [1:20190910.1-0ubuntu91.69.162.6]
User1: can anybody please kick libmojo-ioloop-readwriteprocess-perl out from eoan?
User1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939460
User3: Debian bug 939460 in src:libmojo-ioloop-readwriteprocess-perl "libmojo-ioloop-readwriteprocess-perl: FTBFS and autopkgtest failures with mojo 8.23" [Serious,Open]
User1: this makes something migrate...
User14: apw, ahasenack what needs done to resolve the unsatisfied php7.3 depends for php-defaults?
-queuebot:#ubuntu-release- Unapproved: s390-tools (eoan-proposed/main) [2.11.0-0ubuntu1 => 2.11.0-0ubuntu1] (core)
User12: User14 scroll back a bit :)
User13: User6 component-mismatches just updated, did you do something by hand?
User6: no
User13: ok
User6: I don't even know where to look ...
User15: hello bdmurray or RAOF. We have just completed the SRU validation process for cloud-init v. 29.2.24 Xenial, Bionic and Disco. https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1841099
User3: Launchpad bug 1841099 in cloud-init (Ubuntu Disco) "SRU cloud-init (19.1.1 to 19.2.24): Xenial, Bionic, and Disco" [Undecided,Fix committed]
User15: if there is time today for an SRU review that would be excellent
User14: vorlon, when you get a chance, https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed has some php7.3* packages that need moved to main.  All the corresponding 7.2 versions of the packages are currently in main:  https://paste.ubuntu.com/p/GmRSQtgyqN/.  This should help clear php-defaults from https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#php-defaults
User14: vorlon, and thanks for tending to django-python
User13: User14 php7.3 inaries promoted
User14: vorlon, awesome, thank you again!
User13: User16 python-oslo.config inary removed, that should let python-oslo.i18n in... getting closer
User16: User13 great, thanks!
-queuebot:#ubuntu-release- New binary: wireguard [s390x] (eoan-proposed/none) [0.0.20190905-1] (no packageset)
-queuebot:#ubuntu-release- New binary: wireguard [amd64] (eoan-proposed/none) [0.0.20190905-1] (no packageset)
-queuebot:#ubuntu-release- New binary: wireguard [i386] (eoan-proposed/none) [0.0.20190905-1] (no packageset)
-queuebot:#ubuntu-release- New binary: wireguard [ppc64el] (eoan-proposed/universe) [0.0.20190905-1] (no packageset)
-queuebot:#ubuntu-release- New: accepted wireguard [amd64] (eoan-proposed) [0.0.20190905-1]
-queuebot:#ubuntu-release- New: accepted wireguard [ppc64el] (eoan-proposed) [0.0.20190905-1]
-queuebot:#ubuntu-release- New: accepted wireguard [i386] (eoan-proposed) [0.0.20190905-1]
-queuebot:#ubuntu-release- New: accepted wireguard [s390x] (eoan-proposed) [0.0.20190905-1]
-queuebot:#ubuntu-release- New binary: wireguard [arm64] (eoan-proposed/universe) [0.0.20190905-1] (no packageset)
-queuebot:#ubuntu-release- New binary: wireguard [armhf] (eoan-proposed/universe) [0.0.20190905-1] (no packageset)
-queuebot:#ubuntu-release- New: accepted wireguard [arm64] (eoan-proposed) [0.0.20190905-1]
-queuebot:#ubuntu-release- New: accepted wireguard [armhf] (eoan-proposed) [0.0.20190905-1]
-queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1054.63] (kernel)
-queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1054.63]
-queuebot:#ubuntu-release- Unapproved: bluez (disco-proposed/main) [5.50-0ubuntu2 => 5.50-0ubuntu2.1] (ubuntu-desktop)
-queuebot:#ubuntu-release- Unapproved: bluez (bionic-proposed/main) [5.48-0ubuntu3.1 => 5.48-0ubuntu3.2] (ubuntu-desktop)
User13: cute, python-os-api-ref autopkgtest regression is an autodep8 bug
User13: User1 and rust-rand is dep-wait.
ubuntu-release
Ubuntu IRC