[07:01] <cpaelzer_> rbasak: http://launchpadlibrarian.net/439539273/rdma-core_17.1-1ubuntu0.1_17.1-1ubuntu0.2.diff.gz if you have a chance for some SRU today
[07:11] <cpaelzer_> rbalint: https://wiki.archlinux.org/index.php/Modalias
[07:13] -queuebot:#ubuntu-release- Unapproved: accepted rdma-core [source] (bionic-proposed) [17.1-1ubuntu0.2]
[07:20] -queuebot:#ubuntu-release- Unapproved: ubuntu-drivers-common (bionic-proposed/main) [1:0.5.2.3 => 1:0.5.2.4] (desktop-core, ubuntu-server)
[07:37] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (xenial-proposed) [19.2-36-g059d049c-0ubuntu1~16.04.1]
[07:38] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (bionic-proposed) [19.2-36-g059d049c-0ubuntu1~18.04.1]
[07:39] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (disco-proposed) [19.2-36-g059d049c-0ubuntu1~19.04.1]
[09:03] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.51 => 2.408.52] (desktop-core)
[09:26] <fossfreedom> Quick question, I would like to sync a new version of the gtk arc-theme from unstable to eoan.  Does themes fall under the uife process? Basically gnome-shell 3.34 and xfce4.14 fixes
[09:39] <doko> sforshee: is the riscv64 build fix in 5.3.0-12.13 ?
[09:53] -queuebot:#ubuntu-release- Unapproved: keystone (disco-proposed/main) [2:15.0.0-0ubuntu1.1 => 2:15.0.0-0ubuntu1.2] (openstack, ubuntu-server)
[09:54] <bryyce> I think we've got all the blockers cleared for finishing the php7.3 transition.  Can an archive admin help in dropping 7.2?  C.f. LP: #1842520
[10:01] -queuebot:#ubuntu-release- Unapproved: keystone (bionic-proposed/main) [2:13.0.2-0ubuntu1 => 2:13.0.2-0ubuntu2] (openstack, ubuntu-server)
[10:26] <LocutusOfBorg> fossfreedom, go for it :)
[10:26] <LocutusOfBorg> only new features are not allowed, bugfixes are good to go
[10:27] <LocutusOfBorg> and when the person who syncs is also the debian maintaner, we presume he knows even better his stuff
[12:51] <ahasenack> vorlon: hi, just checking, will php7.2 also be removed from proposed? I see you removed the one in universe, but proposed is still there, is it just lagging?
[13:12] <infinity> cjwatson: Do you want to reupload that livecd-rootfs with -v2.408.50 or wait in queue for the previous SRU to get verified?
[13:13] <vorlon> ahasenack: ah, that was overlooked; removing now
[13:13] <ahasenack> vorlon: thanks!
[13:17] <cjwatson> infinity: Oh right, forgot about that, I'll reupload
[13:18] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.51 => 2.408.52] (desktop-core)
[13:19] <infinity> cjwatson: Ta.
[13:19] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (xenial-proposed) [2.408.52]
[13:47] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (xenial-proposed) [0.122ubuntu8.15]
[13:48] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.52]
[14:13] -queuebot:#ubuntu-release- New binary: rustc [s390x] (eoan-proposed/universe) [1.37.0+dfsg1+llvm-1ubuntu1] (no packageset)
[14:30] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-165.193] (core, kernel)
[14:31] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (disco-proposed/main) [5.0.0-30.32] (core, kernel)
[14:31] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (disco-proposed/main) [5.0.0-30.32] (core, kernel)
[14:32] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (disco-proposed/main) [5.0.0-30.32] (core, kernel)
[15:00] -queuebot:#ubuntu-release- New binary: rustc [ppc64el] (eoan-proposed/universe) [1.37.0+dfsg1+llvm-1ubuntu1] (no packageset)
[15:02] -queuebot:#ubuntu-release- New binary: rustc [amd64] (eoan-proposed/universe) [1.37.0+dfsg1+llvm-1ubuntu1] (no packageset)
[15:03] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (disco-proposed) [5.0.0-30.32]
[15:03] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (disco-proposed) [5.0.0-30.32]
[15:03] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (disco-proposed) [5.0.0-30.32]
[15:04] -queuebot:#ubuntu-release- Unapproved: grep (bionic-proposed/main) [3.1-2 => 3.1-2build1] (core)
[15:12] -queuebot:#ubuntu-release- Unapproved: accepted grep [source] (bionic-proposed) [3.1-2build1]
[15:12] -queuebot:#ubuntu-release- New binary: rustc [i386] (eoan-proposed/universe) [1.37.0+dfsg1+llvm-1ubuntu1] (no packageset)
[15:14] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (bionic-proposed/main) [5.0.0-1021.22~18.04.1] (kernel)
[15:20] <LocutusOfBorg> vorlon, I just saw your imagemagick ping because mentioned on another channel, sorry for that
[15:20] <LocutusOfBorg> next time please forward it again in case I missed it, my bnc sometimes eats messages
[15:20] <LocutusOfBorg> apologizes
[15:24] <rbalint> hi, i just would like confirmation that wireshark sync to next upstream point release does not need FFe since they are mostly bugfix releases and we also follow them in security updates
[15:25] <rbalint> if no one objects i'll sync it when it migrates to Debian testing
[15:26] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-165.193]
[15:27] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (bionic-proposed) [5.0.0-1021.22~18.04.1]
[15:30] <cyphermox> hi; please remove node-prismjs; it's blocked on non-existing node-clipboard, had RC bugs in Debian on that, only in unstable and blocked there for >200 days
[15:52] <LocutusOfBorg> sforshee, linux-signed FTBFS and now nothing in the eoan archive can build... I retried the failed builds, lets see what happens
[15:52] <LocutusOfBorg> (the error was after 1 minute of build about not being able to retrieve SHA256SUM hashes)
[15:55] <LocutusOfBorg> ok now a give-back seems to have worked, I blame some network glitch...
[15:57] -queuebot:#ubuntu-release- New binary: linux-signed [s390x] (eoan-proposed/main) [5.3.0-12.13] (core, kernel)
[16:00] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (eoan-proposed/main) [5.3.0-12.13] (core, kernel)
[16:00] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (eoan-proposed/main) [5.3.0-12.13] (core, kernel)
[16:00] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (eoan-proposed/main) [5.3.0-12.13] (core, kernel)
[16:26] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (eoan-proposed) [5.3.0-12.13]
[16:26] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (eoan-proposed) [5.3.0-12.13]
[16:26] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (eoan-proposed) [5.3.0-12.13]
[16:26] -queuebot:#ubuntu-release- New: accepted linux-signed [s390x] (eoan-proposed) [5.3.0-12.13]
[16:55] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (disco-proposed/main) [5.0.0-1021.22] (core, kernel)
[20:19] -queuebot:#ubuntu-release- New binary: rustc [armhf] (eoan-proposed/universe) [1.37.0+dfsg1+llvm-1ubuntu1] (no packageset)
[21:08] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (disco-proposed) [5.0.0-1021.22]
[21:13] -queuebot:#ubuntu-release- New binary: rustc [arm64] (eoan-proposed/universe) [1.37.0+dfsg1+llvm-1ubuntu1] (no packageset)
[21:54] <vorlon> LocutusOfBorg: no worries.  so what's the answer on imagemagick?  Should we revert the revert of the security fix?
[22:57] -queuebot:#ubuntu-release- New binary: linux-signed-oem-osp1 [amd64] (bionic-proposed/universe) [5.0.0-1023.25] (no packageset)
[22:57] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (bionic-proposed/main) [4.15.0-1026.29] (kernel)
[22:57] -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1057.66] (kernel)
[23:16] <LocutusOfBorg> vorlon, I already did
[23:16] <LocutusOfBorg> I thought there was no hurry since the MIR was still ongoing
[23:17] <LocutusOfBorg> but I happily reverted it now, and I'm uploading in my ppa a list of packages that depends on imagemagick, and I'll give security team a full review of what FTBFS because of this change