On Sunday, 19 June 2022 04:54:26 BST Alan Grimes wrote: [snippage of long prose ...]
> Example: > > Old way: > > "My boot drive is plugged into this port on the motherboard" > > New way: > > Spend hours figuring out what your UUID is, create a physical pocket > folder (which you will subsequently have to store and manage) with the > UUID which is long and complex and copy it by hand, very carefully, then > set that up in your mtab.... It doesn't take hours to run 'blkid'. > Example: > > Old way: "My network printer is at this IP address" > > New way: > > Master a list of 5-6 obscure and arcane packages that let you assign > "human friendly" network names to devices and then get all those > packages working with each other so you can print. Yeah, it looks more > like christmass tree wiring than a solution to a problem, You'll be > doing it again from scratch next month when we decide to change it again > for no reason and No, you can't print using the old way. > > Ie, the printer I spent $400 on so that I could print from anywhere in > my house only works with my windows computer because I made the mistake > of updating CUPS. I have always been using an IP address to specify my printer. In a different topology with multiple printers and regularly changing users/PCs I would consider a different more automated approach. > It's only been 3 months innce I updated last so therefore I'm hurting > BAD tonight. I had to update the hack I used last time to get around the > libicuuc fuckup by implementing the same hack again but version > bumped... (symlink 1.71.1 to 1.70)... It seemed gung ho about python > 3.11 but it turned out that 3.11 is still beta and that I should ignore > it. > > The maintainers of steam overlay seem to have given up, so I used layman > to -d it and now I get > !!! Invalid PORTDIR_OVERLAY (not a dir): '/var/lib/layman/steam-overlay' > each time I invoke emerge... Take a look at: https://wiki.gentoo.org/wiki/Eselect/Repository > What's killing me dead, however is: > >>> Running pre-merge checks for www-client/chromium-104.0.5110.0 > > * sys-devel/clang:14 is missing! Cannot use LLVM slot 14 ... > * =sys-devel/lld-13* is missing! Cannot use LLVM slot 13 ... > * =sys-devel/lld-12* is missing! Cannot use LLVM slot 12 ... > * =sys-devel/lld-11* is missing! Cannot use LLVM slot 11 ... > * sys-devel/clang:10 is missing! Cannot use LLVM slot 10 ... > * sys-devel/clang:9 is missing! Cannot use LLVM slot 9 ... > * sys-devel/clang:8 is missing! Cannot use LLVM slot 8 ... > * ERROR: www-client/chromium-104.0.5110.0::gentoo failed (pretend phase): > * No LLVM slot <= 14 satisfying the package's dependencies found > installed! Err ... ~ $ eix -l chromium | grep '104.0.5110.0' [M]~ 104.0.5110.0 (0/dev) [+X component-build cups custom-cflags debug gtk4 +hangouts headless +js-type-check kerberos libcxx lto +official pgo pic +proprietary-codecs pulseaudio screencast selinux +suid +system-ffmpeg +system-harfbuzz +system-icu +system-png vaapi wayland widevine CPU_FLAGS_ARM="neon" L10N="+af +am +ar +bg +bn +ca +cs +da +de +el +en-GB +es +es-419 +et +fa +fi +fil +fr +gu +he +hi +hr +hu +id +it +ja +kn +ko +lt +lv +ml +mr +ms +nb +nl +pl +pt-BR +pt-PT +ro +ru +sk +sl +sr +sv +sw +ta +te +th +tr +uk +ur +vi +zh-CN +zh-TW"] ["component-build? ( !suid !libcxx ) screencast? ( wayland ) !headless? ( || ( X wayland ) ) pgo? ( X !wayland )"] So, you're trying to install a masked version of chromium, which may or may not ever make it into the testing/stable tree without further development work on it and any one of its dependencies and you blame some penguin for the result? > * > * Call stack: > * ebuild.sh, line 127: Called pkg_pretend > * chromium-104.0.5110.0.ebuild, line 283: Called pre_build_checks > * chromium-104.0.5110.0.ebuild, line 243: Called llvm_pkg_setup > * llvm.eclass, line 201: Called get_llvm_prefix '14' > * llvm.eclass, line 180: Called die > * The specific snippet of code: > * die "No LLVM slot${1:+ <= ${1}} satisfying the package's > dependencies found installed!" [snip ...] > >>> Failed to emerge www-client/chromium-104.0.5110.0, Log file: > ########################## > > > Slot conflict??? > > No problem! I'll just go to eselect and pick a different slot......... > > > Oh wait, that was the OLD way of selecting slots... I went searching for > an explanation for how to set it up and it was like: [snip ...] You should be able to install a specific slot, but you may have to keyword it if you're on a stable arch. Starting with lld, clang, llvm and whatever else may be needed. However, why would you want to try a masked package - unless you have the time, knowledge and inclination beyond authoring long prose posts in a mailing list to contribute to its development? > KDE will keep me busy the rest of the night, I only use a handful of its > utilities and don't even know how to set it up as a window manager but > it likes to version bump its packages several times an hour and cause > emerge conflicts just to piss me off... If you use (mostly) stable arch packages emerge conflicts tend to be a rare event.
signature.asc
Description: This is a digitally signed message part.
