Installing www-client/torbrowser-68.10.0_p951 leads to a fatal error that it requires clang:10. The oldest available version of clang is 11. Reproducible: Always Steps to Reproduce: 1. sudo emerge torbrowser 2. Ammend package.use as necessary 3. Calculating dependencies... done! emerge: there are no ebuilds to satisfy "sys-devel/clang:10". Actual Results: sudo emerge torbrowser Password: Calculating dependencies... done! The following USE changes are necessary to proceed: (see "package.use" in the portage(5) man page for more details) # required by www-client/torbrowser-68.10.0_p951::torbrowser # required by torbrowser (argument) >=media-libs/libpng-1.6.37-r2 apng # required by www-client/torbrowser-68.10.0_p951::torbrowser[system-libvpx] # required by torbrowser (argument) =media-libs/libvpx-1.7.0-r1 postproc # required by www-client/torbrowser-68.10.0_p951::torbrowser[system-sqlite] # required by torbrowser (argument) >=dev-db/sqlite-3.37.0 secure-delete Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT). Carefully examine the list of proposed changes, paying special attention to mask or keyword changes that may expose experimental or unstable packages. * In order to avoid wasting time, backtracking has terminated early * due to the above autounmask change(s). The --autounmask-backtrack=y * option can be used to force further backtracking, but there is no * guarantee that it will produce a solution. emerge: there are no ebuilds to satisfy "sys-devel/clang:10". Expected Results: After amending package.use, torbrowser should install. The lack of clang version 10 causes it to fail. eix sys-devel/clang [I] sys-devel/clang Available versions: (11) 11.1.0(11/11.1)^t (12) 12.0.1^t (13) 13.0.0^t **13.0.1_rc1^t **13.0.1.9999*l^t (14) **14.0.0.9999*l^t {debug default-compiler-rt default-libcxx default-lld doc llvm-libunwind +static-analyzer test xml ABI_MIPS="n32 n64 o32" ABI_S390="32 64" ABI_X86="32 64 x32" KERNEL="FreeBSD" LLVM_TARGETS="AArch64 AMDGPU ARC ARM AVR BPF CSKY Hexagon Lanai M68k MSP430 Mips NVPTX PowerPC RISCV Sparc SystemZ VE WebAssembly X86 XCore" PYTHON_SINGLE_TARGET="python3_8 python3_9 python3_10"} Installed versions: 13.0.0(13)^t(11:00:58 PM 2021-11-25)(static-analyzer xml -debug -default-compiler-rt -default-libcxx -default-lld -doc -llvm-libunwind -test ABI_MIPS="-n32 -n64 -o32" ABI_S390="-32 -64" ABI_X86="64 -32 -x32" KERNEL="-FreeBSD" LLVM_TARGETS="AMDGPU BPF NVPTX X86 -AArch64 -ARC -ARM -AVR -CSKY -Hexagon -Lanai -M68k -MSP430 -Mips -PowerPC -RISCV -Sparc -SystemZ -VE -WebAssembly -XCore" PYTHON_SINGLE_TARGET="python3_9 -python3_8 -python3_10") Homepage: https://llvm.org/ Description: C language family frontend for LLVM [I] sys-devel/clang-common Available versions: 11.1.0 12.0.1 13.0.0 **13.0.1_rc1 **13.0.1.9999*l **14.0.0.9999*l Installed versions: 13.0.0(09:12:10 AM 2021-11-25) Homepage: https://llvm.org/ Description: Common files shared between multiple slots of clang [I] sys-devel/clang-runtime Available versions: (11.1.0) 11.1.0 (12.0.1) 12.0.1 (13.0.0) 13.0.0 (13.0.1) **13.0.1_rc1*l **13.0.1.9999*l (14.0.0) **14.0.0.9999*l {+compiler-rt libcxx openmp +sanitize ABI_MIPS="n32 n64 o32" ABI_S390="32 64" ABI_X86="32 64 x32"} Installed versions: 13.0.0(13.0.0)(11:03:54 PM 2021-11-25)(compiler-rt openmp sanitize -libcxx ABI_MIPS="-n32 -n64 -o32" ABI_S390="-32 -64" ABI_X86="32 64 -x32") Homepage: https://clang.llvm.org/ Description: Meta-ebuild for clang runtime libraries
That is a very old version of Tor Browser. I'm not sure you want it tbh. Huge amount of vulnerabilities
The current version in the overlay is torbrowser-91.4.1_p11003 Please install the newest version. This should work with the clang-{11,12,13} See https://github.com/MeisterP/torbrowser-overlay/tree/master/www-client
Ah, this is invalid then. That version doesn't exist in ::torbrowser.
If an overlay is required to use it, I'll make the same suggestion I did with the torbrowser-launcher ebuild. Add something to the error message stating that you need to use an overlay and not "vanilla" Gentoo dists. Maybe even remove the ebuilds from the "vanilla" dists. eix torbrowser * www-client/torbrowser [1] Available versions: (~)68.10.0_p951 {clang custom-cflags custom-optimization dbus hardened pulseaudio startup-notification +system-av1 +system-harfbuzz +system-icu +system-jpeg +system-libevent +system-libvpx +system-sqlite +system-webp CPU_FLAGS_X86="avx2"} Homepage: https://www.torproject.org/projects/torbrowser.html https://gitweb.torproject.org/tor-browser.git Description: The Tor Browser
(In reply to B Nice from comment #4) > If an overlay is required to use it, I'll make the same suggestion I did > with the torbrowser-launcher ebuild. Add something to the error message > stating that you need to use an overlay and not "vanilla" Gentoo dists. > Maybe even remove the ebuilds from the "vanilla" dists. > > eix torbrowser > * www-client/torbrowser [1] > Available versions: (~)68.10.0_p951 {clang custom-cflags > custom-optimization dbus hardened pulseaudio startup-notification > +system-av1 +system-harfbuzz +system-icu +system-jpeg +system-libevent > +system-libvpx +system-sqlite +system-webp CPU_FLAGS_X86="avx2"} > Homepage: > https://www.torproject.org/projects/torbrowser.html > https://gitweb.torproject.org/tor-browser.git > Description: The Tor Browser That doesn't make sense though. That ebuild is not in the "vanilla dists". It's _coming from_ an overlay you have enabled that you haven't synced. You can just remove/disable it.
(In reply to B Nice from comment #4) > * www-client/torbrowser [1] That [1] in the output of eix tells you that the ebuild is from an overlay. Further down in the eix output it tells you from which overlay and where that overay is stored on your filesystem. (That part is missing in your post here though) Assuming it's the same as in https://bugs.gentoo.org/830130#c3 it would read > [1] "torbrowser" /var/lib/layman/torbrowser Which tells you that the ebuild is from the torbrowser overlay and stored in /var/lib/layman/torbrowser
Apologies. You are correct, I have layman installed. No idea when or why or how, but it is there.
(In reply to B Nice from comment #7) > Apologies. You are correct, I have layman installed. No idea when or why > or how, but it is there. No worries. Bugzilla is not a good place to assist you further though. If you need help with managing overlays, have a look at https://www.gentoo.org/support/
