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