User1: User2 can you kick grub2 along pls
User1: (at some point in the next 24 hrs, no real hurry!)
-queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (eoan-proposed) [2.04-1ubuntu5]
-queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (eoan-proposed) [2.04-1ubuntu5]
User2: User1 ^^
User1: User2 thanks
User1: User2 why does that happen, is it just so an AA can check there is a grub-signed upload waiting?
User2: User1 it's so that objects don't get signed with the UEFI key without an AA signing off on it
User1: User2 ah makes sense
-queuebot:#ubuntu-release- New binary: r-cran-ica [amd64] (eoan-proposed/none) [1.0-2-1] (no packageset)
-queuebot:#ubuntu-release- New binary: r-cran-lsei [i386] (eoan-proposed/none) [1.2-0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: r-cran-lsei [amd64] (eoan-proposed/none) [1.2-0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: r-cran-metap [amd64] (eoan-proposed/none) [1.1-1] (no packageset)
-queuebot:#ubuntu-release- New binary: r-bioc-tximport [amd64] (eoan-proposed/none) [1.12.3+dfsg-1] (no packageset)
-queuebot:#ubuntu-release- New binary: r-cran-lsei [s390x] (eoan-proposed/none) [1.2-0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: r-cran-future.apply [amd64] (eoan-proposed/universe) [1.3.0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: r-cran-tsne [amd64] (eoan-proposed/universe) [0.1-3-1] (no packageset)
-queuebot:#ubuntu-release- New binary: r-cran-lsei [armhf] (eoan-proposed/universe) [1.2-0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: r-cran-lsei [arm64] (eoan-proposed/universe) [1.2-0-1] (no packageset)
-queuebot:#ubuntu-release- New binary: r-cran-lsei [ppc64el] (eoan-proposed/universe) [1.2-0-1] (no packageset)
User3: User2 Debian actually ships a fork of compiz, while we ship mainstream compiz. We do not need compiz-plugins-* source packages at all because we build the corresponding binaries from compiz source.
User3: I think src:compiz-plugins-experimental should be removed from eoan-proposed and added to sync blacklist.
User3: To clarify, upstream compiz is https://launchpad.net/compiz, Debian uses https://gitlab.com/compiz aka compiz-reloaded.
User4: User3 Is there a reason we can't move to using the Debian sources and maintain one less thing in Ubuntu?
-queuebot:#ubuntu-release- New binary: linux-signed [amd64] (disco-proposed/main) [5.0.0-26.27] (core, kernel)
-queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (disco-proposed/main) [5.0.0-26.27] (core, kernel)
-queuebot:#ubuntu-release- New binary: linux-signed [arm64] (disco-proposed/main) [5.0.0-26.27] (core, kernel)
-queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (disco-proposed) [5.0.0-26.27]
-queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (disco-proposed) [5.0.0-26.27]
-queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (disco-proposed) [5.0.0-26.27]
User3: User4 That would mean erasing 10 years work that Canonical did on refactoring Compiz and rewriting it in C++ (compiz-reloaded is based on compiz 0.8). Also Unity won't work with compiz-reloaded.
User4: User3 "Erasing work" is just sunk cost fallacy rearing its ugly head, but the "won't work with Unity" point is the important bit.
User4: User3 Would still be nice to have Debian and Ubuntu shipping vaguely the same code, but maybe the argument needs to be made in the other direction then.
User5: well compiz is such an overloaded term..... each series and forks of it, should have had a separate name =/
User3: Debian tried 0.9 but then reverted to 0.8, unfortunately I don't know their reasons.
User3: The only explanation I can find is in Debian #907640
User6: Debian bug 907640 in compiz "compiz: Migrating to compiz-reloaded?" [Important,Fixed] http://bugs.debian.org/907640
User3: âThe launchpad upstream for compiz has switched to light maintenance mode and will not make further development since Ubuntu has stopped using it.â
User3: I am not using compiz or unity myself, so I'm not the person to make any decision about their future.
-queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (disco-proposed/main) [5.0.0-1014.14] (core, kernel)
-queuebot:#ubuntu-release- New binary: qtdoc-opensource-src [i386] (eoan-proposed/universe) [5.12.2-1] (kubuntu, qt5)
-queuebot:#ubuntu-release- New binary: qtdoc-opensource-src [ppc64el] (eoan-proposed/universe) [5.12.2-1] (kubuntu, qt5)
-queuebot:#ubuntu-release- New binary: qtdoc-opensource-src [s390x] (eoan-proposed/universe) [5.12.2-1] (kubuntu, qt5)
-queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (disco-proposed) [5.0.0-1014.14]
-queuebot:#ubuntu-release- New binary: qtdoc-opensource-src [armhf] (eoan-proposed/universe) [5.12.2-1] (kubuntu, qt5)
-queuebot:#ubuntu-release- New binary: qtdoc-opensource-src [amd64] (eoan-proposed/universe) [5.12.2-1] (kubuntu, qt5)
-queuebot:#ubuntu-release- New binary: qtdoc-opensource-src [arm64] (eoan-proposed/universe) [5.12.2-1] (kubuntu, qt5)
-queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-59.66] (core, kernel)
-queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-59.66] (core, kernel)
User7: can we get a newer meson in bionic, please?
User8: tjaalton, you could be the one doing that SRU if you need it :)
User8: I don't think we have a specific maintainer for it
User7: I'll try
User8: tjaalton, is it strictly needed? for fwupdate we patch out the meson build thing to be able to build with an older version which was easier to do
User7: we miss changes like https://github.com/mesonbuild/meson/commit/12bac512f6497e46ada8ed980cbcb1631506691c which result in asserts in DRI drivers, for instance
User8: :-/
User8: the problem is that meson updates include some feature and behaviour changes so that's not really trivial to SRU
-queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-59.66]
-queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-59.66]
User7: could be
-queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (bionic-proposed/main) [5.0.0-26.27~18.04.1] (kernel)
-queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (bionic-proposed/main) [5.0.0-26.27~18.04.1] (kernel)
-queuebot:#ubuntu-release- New binary: linux-signed-hwe [arm64] (bionic-proposed/main) [5.0.0-26.27~18.04.1] (kernel)
-queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (bionic-proposed) [5.0.0-26.27~18.04.1]
-queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (bionic-proposed) [5.0.0-26.27~18.04.1]
-queuebot:#ubuntu-release- New: accepted linux-signed-hwe [arm64] (bionic-proposed) [5.0.0-26.27~18.04.1]
-queuebot:#ubuntu-release- Unapproved: thermald (bionic-proposed/main) [1.7.0-5ubuntu3 => 1.7.0-5ubuntu4] (core)
-queuebot:#ubuntu-release- Unapproved: rejected thermald [source] (bionic-proposed) [1.7.0-5ubuntu4]
-queuebot:#ubuntu-release- Unapproved: thermald (bionic-proposed/main) [1.7.0-5ubuntu3 => 1.7.0-5ubuntu4] (core)
-queuebot:#ubuntu-release- Unapproved: accepted thermald [source] (bionic-proposed) [1.7.0-5ubuntu4]
-queuebot:#ubuntu-release- Unapproved: thermald (bionic-proposed/main) [1.7.0-5ubuntu4 => 1.7.0-5ubuntu5] (core)
-queuebot:#ubuntu-release- Unapproved: accepted thermald [source] (bionic-proposed) [1.7.0-5ubuntu5]
-queuebot:#ubuntu-release- New binary: linux-signed-gke-5.0 [amd64] (bionic-proposed/universe) [5.0.0-1014.14~18.04.1] (kernel)
-queuebot:#ubuntu-release- New binary: linux-signed-gke-4.15 [amd64] (bionic-proposed/main) [4.15.0-1041.43] (no packageset)
-queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-160.188] (core, kernel)
-queuebot:#ubuntu-release- New: accepted linux-signed-gke-4.15 [amd64] (bionic-proposed) [4.15.0-1041.43]
-queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-160.188]
-queuebot:#ubuntu-release- New: accepted linux-signed-gke-5.0 [amd64] (bionic-proposed) [5.0.0-1014.14~18.04.1]
User2: teward|web: the first thing to do is check whether the failure also happens without the new nginx
User2: and if it is, get the release team to add a 'badtest' hint, and decouple resolving this autopkgtest failure from the nginx package migration
User2: teward|web: but I also see the arm64 autopkgtest failed in connection with an apache2 upload, so maybe it's just a flaky test
User2: sure, hence 'flaky'
User2: well, I've already triggered them on the Ubuntu infra; if they pass the second time, nginx gets let through automatically
User2: I only see one amd64 failure listed on http://autopkgtest.ubuntu.com/packages/l/lemonldap-ng/eoan/amd64
User2: teward|web: both the failure and the repoke listed there are with apache2 as a trigger, not nginx
User2: the nginx/arm64 failure doesn't even show up on the report yet (because the report generation sometimes lags the update_excuses generation)
User9: sforshee, User10 binutils and gcc-9 blocked by linux autopkg test failures
User10: doko, aware, if those are the last issues for those two package let me knwo and i'll hint them out
User9: User10 they are
User10: doko, hinted
-queuebot:#ubuntu-release- Unapproved: stress-ng (bionic-proposed/universe) [0.09.25-1ubuntu2 => 0.09.25-1ubuntu3] (no packageset)
-queuebot:#ubuntu-release- New binary: libinputsynth [amd64] (eoan-proposed/none) [0.12.1-1] (no packageset)
-queuebot:#ubuntu-release- New binary: kdeplasma-applets-xrdesktop [amd64] (eoan-proposed/none) [0.12.1-1] (no packageset)
-queuebot:#ubuntu-release- New binary: pylint-flask [amd64] (eoan-proposed/universe) [0.5-3] (no packageset)
-queuebot:#ubuntu-release- New binary: libinputsynth [i386] (eoan-proposed/none) [0.12.1-1] (no packageset)
-queuebot:#ubuntu-release- New binary: libinputsynth [arm64] (eoan-proposed/universe) [0.12.1-1] (no packageset)
-queuebot:#ubuntu-release- New binary: volk [i386] (eoan-proposed/universe) [2.0.0-2] (no packageset)
-queuebot:#ubuntu-release- New binary: volk [amd64] (eoan-proposed/universe) [2.0.0-2] (no packageset)
-queuebot:#ubuntu-release- New binary: libinputsynth [s390x] (eoan-proposed/universe) [0.12.1-1] (no packageset)
-queuebot:#ubuntu-release- New binary: volk [s390x] (eoan-proposed/universe) [2.0.0-2] (no packageset)
-queuebot:#ubuntu-release- New binary: libinputsynth [armhf] (eoan-proposed/universe) [0.12.1-1] (no packageset)
-queuebot:#ubuntu-release- New binary: volk [armhf] (eoan-proposed/universe) [2.0.0-2] (no packageset)
-queuebot:#ubuntu-release- New binary: volk [arm64] (eoan-proposed/universe) [2.0.0-2] (no packageset)
-queuebot:#ubuntu-release- New binary: libinputsynth [ppc64el] (eoan-proposed/universe) [0.12.1-1] (no packageset)
-queuebot:#ubuntu-release- New binary: volk [ppc64el] (eoan-proposed/universe) [2.0.0-2] (no packageset)
ubuntu-release
Ubuntu IRC