/srv/irclogs.ubuntu.com/2019/09/18/#ubuntu-release.txt

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 today07:01
cpaelzer_rbalint: https://wiki.archlinux.org/index.php/Modalias07:11
-queuebot:#ubuntu-release- Unapproved: accepted rdma-core [source] (bionic-proposed) [17.1-1ubuntu0.2]07:13
-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:20
-queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (xenial-proposed) [19.2-36-g059d049c-0ubuntu1~16.04.1]07:37
-queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (bionic-proposed) [19.2-36-g059d049c-0ubuntu1~18.04.1]07:38
-queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (disco-proposed) [19.2-36-g059d049c-0ubuntu1~19.04.1]07:39
-queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.51 => 2.408.52] (desktop-core)09:03
fossfreedomQuick 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 fixes09:26
dokosforshee: is the riscv64 build fix in 5.3.0-12.13 ?09:39
-queuebot:#ubuntu-release- Unapproved: keystone (disco-proposed/main) [2:15.0.0-0ubuntu1.1 => 2:15.0.0-0ubuntu1.2] (openstack, ubuntu-server)09:53
bryyceI 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: #184252009:54
ubot5Launchpad bug 1842520 in php7.2 (Ubuntu) "Remove "php7.2" from Eoan, which has transitioned to php7.3" [Undecided,New] https://launchpad.net/bugs/184252009:54
-queuebot:#ubuntu-release- Unapproved: keystone (bionic-proposed/main) [2:13.0.2-0ubuntu1 => 2:13.0.2-0ubuntu2] (openstack, ubuntu-server)10:01
LocutusOfBorgfossfreedom, go for it :)10:26
LocutusOfBorgonly new features are not allowed, bugfixes are good to go10:26
LocutusOfBorgand when the person who syncs is also the debian maintaner, we presume he knows even better his stuff10:27
ahasenackvorlon: 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?12:51
infinitycjwatson: Do you want to reupload that livecd-rootfs with -v2.408.50 or wait in queue for the previous SRU to get verified?13:12
vorlonahasenack: ah, that was overlooked; removing now13:13
ahasenackvorlon: thanks!13:13
cjwatsoninfinity: Oh right, forgot about that, I'll reupload13:17
-queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.51 => 2.408.52] (desktop-core)13:18
infinitycjwatson: Ta.13:19
-queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (xenial-proposed) [2.408.52]13:19
-queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (xenial-proposed) [0.122ubuntu8.15]13:47
-queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.52]13:48
-queuebot:#ubuntu-release- New binary: rustc [s390x] (eoan-proposed/universe) [1.37.0+dfsg1+llvm-1ubuntu1] (no packageset)14:13
-queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-165.193] (core, kernel)14:30
-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:31
-queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (disco-proposed/main) [5.0.0-30.32] (core, kernel)14:32
-queuebot:#ubuntu-release- New binary: rustc [ppc64el] (eoan-proposed/universe) [1.37.0+dfsg1+llvm-1ubuntu1] (no packageset)15:00
-queuebot:#ubuntu-release- New binary: rustc [amd64] (eoan-proposed/universe) [1.37.0+dfsg1+llvm-1ubuntu1] (no packageset)15:02
-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:03
-queuebot:#ubuntu-release- Unapproved: grep (bionic-proposed/main) [3.1-2 => 3.1-2build1] (core)15:04
-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:12
-queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (bionic-proposed/main) [5.0.0-1021.22~18.04.1] (kernel)15:14
LocutusOfBorgvorlon, I just saw your imagemagick ping because mentioned on another channel, sorry for that15:20
LocutusOfBorgnext time please forward it again in case I missed it, my bnc sometimes eats messages15:20
LocutusOfBorgapologizes15:20
rbalinthi, 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 updates15:24
rbalintif no one objects i'll sync it when it migrates to Debian testing15:25
-queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-165.193]15:26
-queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (bionic-proposed) [5.0.0-1021.22~18.04.1]15:27
cyphermoxhi; 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 days15:30
LocutusOfBorgsforshee, linux-signed FTBFS and now nothing in the eoan archive can build... I retried the failed builds, lets see what happens15:52
LocutusOfBorg(the error was after 1 minute of build about not being able to retrieve SHA256SUM hashes)15:52
LocutusOfBorgok now a give-back seems to have worked, I blame some network glitch...15:55
-queuebot:#ubuntu-release- New binary: linux-signed [s390x] (eoan-proposed/main) [5.3.0-12.13] (core, kernel)15:57
-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:00
-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:26
-queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (disco-proposed/main) [5.0.0-1021.22] (core, kernel)16:55
-queuebot:#ubuntu-release- New binary: rustc [armhf] (eoan-proposed/universe) [1.37.0+dfsg1+llvm-1ubuntu1] (no packageset)20:19
-queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (disco-proposed) [5.0.0-1021.22]21:08
-queuebot:#ubuntu-release- New binary: rustc [arm64] (eoan-proposed/universe) [1.37.0+dfsg1+llvm-1ubuntu1] (no packageset)21:13
vorlonLocutusOfBorg: no worries.  so what's the answer on imagemagick?  Should we revert the revert of the security fix?21:54
-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)22:57
LocutusOfBorgvorlon, I already did23:16
LocutusOfBorgI thought there was no hurry since the MIR was still ongoing23:16
LocutusOfBorgbut 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 change23:17

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!