QA: other One or more CMake variables were not used by the project: ENABLE_PAM ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome_systemd-20201001-162923 -------------------------------------------------------------------
Created attachment 663664 [details] etc.portage.tbz2
The new tool vncsession used to start the service (see bug #746227) make use of pam, so it is no more optional.
As one of those weird people who doesn't use PAM, would it make sense to block building of vncsession if the use flag is turned off? (I don't know if it's easy to tell it not to build that while including everything else.)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9dc0ec55803692786e6538bca4a12b0102e775f3 commit 9dc0ec55803692786e6538bca4a12b0102e775f3 Author: Sam James <sam@gentoo.org> AuthorDate: 2021-12-07 23:16:18 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-12-07 23:16:42 +0000 net-misc/tigervnc: add 1.12.0 (still masked) Note that this doesn't yet fix the xsession handling stuff, but am looking to see what we can do about it. Bug: https://bugs.gentoo.org/746227 Closes: https://bugs.gentoo.org/746359 Closes: https://bugs.gentoo.org/746365 Signed-off-by: Sam James <sam@gentoo.org> net-misc/tigervnc/Manifest | 1 + net-misc/tigervnc/tigervnc-1.12.0.ebuild | 184 +++++++++++++++++++++++++++++++ net-misc/tigervnc/tigervnc-9999.ebuild | 9 +- 3 files changed, 189 insertions(+), 5 deletions(-)
-pam support was removed upstream: https://github.com/TigerVNC/tigervnc/commit/d80817f101d1b3f1a9b1c5ec268f28fffa2d75f9
*** Bug 746365 has been marked as a duplicate of this bug. ***
