1 |
I probably owe you guys an appology which is not forthcoming, at least |
2 |
not tonight for obvious reasons. Instead, lets me explain my problem |
3 |
solving procedure. |
4 |
|
5 |
|
6 |
At this point in time, if you have a problem, especially on linux, it is |
7 |
almost never the problem that existed before a penguin tried to solve it |
8 |
for you. Instead, the problem you are facing is the problem caused when |
9 |
either a penguin or a whole flock of penguins sanctamoniously decided |
10 |
that you needed a solution and that this solution would be installed on |
11 |
your system without your intervention, or knowledge or concent. |
12 |
Occasionally they get away wtith this and your life gets a little easier |
13 |
and you are none the wiser. Usually, however, their solution to the |
14 |
thing that wasn't really bothering you in the first place fails |
15 |
spectacularly and spoils your whole week. |
16 |
|
17 |
Ok, what are your options? |
18 |
|
19 |
A: Figure out what brand of dope the penguin was on and what dose, ratio |
20 |
of dope to vodka, and get on precisely the same prescription to get in |
21 |
just the right mindset to try to understand how their crappy software |
22 |
was supposed to work so you can fix it. |
23 |
|
24 |
B. Exterminate the penguin's software from your computer so that you can |
25 |
experience the underlying problem in its rawest and most brutal form and |
26 |
find that it's not even worth solving or that it admits an utterly |
27 |
trivial solution that, at least, makes sense to you and that you won't |
28 |
have any trouble maintaining for the long haul. |
29 |
|
30 |
|
31 |
For me, choice A is always always always wrong. The computer is supposed |
32 |
to work for you, not the other way around. If you are spending hours, or |
33 |
even weeks of your rotten miserable life chasing down obscure answers to |
34 |
questions you shouldn't even have, then you are doing computing wrong |
35 |
and need to stop, take two steps back, and figure out what your real |
36 |
problem is. |
37 |
|
38 |
I get angry when Linux does not let me do that. =| |
39 |
|
40 |
Instead, the penguins seem obsessed with inventing more and more garbage |
41 |
that I need to manage. |
42 |
|
43 |
Example: |
44 |
|
45 |
Old way: |
46 |
|
47 |
"My boot drive is plugged into this port on the motherboard" |
48 |
|
49 |
New way: |
50 |
|
51 |
Spend hours figuring out what your UUID is, create a physical pocket |
52 |
folder (which you will subsequently have to store and manage) with the |
53 |
UUID which is long and complex and copy it by hand, very carefully, then |
54 |
set that up in your mtab.... |
55 |
|
56 |
Example: |
57 |
|
58 |
Old way: "My network printer is at this IP address" |
59 |
|
60 |
New way: |
61 |
|
62 |
Master a list of 5-6 obscure and arcane packages that let you assign |
63 |
"human friendly" network names to devices and then get all those |
64 |
packages working with each other so you can print. Yeah, it looks more |
65 |
like christmass tree wiring than a solution to a problem, You'll be |
66 |
doing it again from scratch next month when we decide to change it again |
67 |
for no reason and No, you can't print using the old way. |
68 |
|
69 |
Ie, the printer I spent $400 on so that I could print from anywhere in |
70 |
my house only works with my windows computer because I made the mistake |
71 |
of updating CUPS. |
72 |
|
73 |
|
74 |
It's only been 3 months innce I updated last so therefore I'm hurting |
75 |
BAD tonight. I had to update the hack I used last time to get around the |
76 |
libicuuc fuckup by implementing the same hack again but version |
77 |
bumped... (symlink 1.71.1 to 1.70)... It seemed gung ho about python |
78 |
3.11 but it turned out that 3.11 is still beta and that I should ignore |
79 |
it. |
80 |
|
81 |
The maintainers of steam overlay seem to have given up, so I used layman |
82 |
to -d it and now I get |
83 |
!!! Invalid PORTDIR_OVERLAY (not a dir): '/var/lib/layman/steam-overlay' |
84 |
each time I invoke emerge... |
85 |
|
86 |
What's killing me dead, however is: |
87 |
|
88 |
>>> Running pre-merge checks for www-client/chromium-104.0.5110.0 |
89 |
* sys-devel/clang:14 is missing! Cannot use LLVM slot 14 ... |
90 |
* =sys-devel/lld-13* is missing! Cannot use LLVM slot 13 ... |
91 |
* =sys-devel/lld-12* is missing! Cannot use LLVM slot 12 ... |
92 |
* =sys-devel/lld-11* is missing! Cannot use LLVM slot 11 ... |
93 |
* sys-devel/clang:10 is missing! Cannot use LLVM slot 10 ... |
94 |
* sys-devel/clang:9 is missing! Cannot use LLVM slot 9 ... |
95 |
* sys-devel/clang:8 is missing! Cannot use LLVM slot 8 ... |
96 |
* ERROR: www-client/chromium-104.0.5110.0::gentoo failed (pretend phase): |
97 |
* No LLVM slot <= 14 satisfying the package's dependencies found |
98 |
installed! |
99 |
* |
100 |
* Call stack: |
101 |
* ebuild.sh, line 127: Called pkg_pretend |
102 |
* chromium-104.0.5110.0.ebuild, line 283: Called pre_build_checks |
103 |
* chromium-104.0.5110.0.ebuild, line 243: Called llvm_pkg_setup |
104 |
* llvm.eclass, line 201: Called get_llvm_prefix '14' |
105 |
* llvm.eclass, line 180: Called die |
106 |
* The specific snippet of code: |
107 |
* die "No LLVM slot${1:+ <= ${1}} satisfying the package's |
108 |
dependencies found installed!" |
109 |
* |
110 |
* If you need support, post the output of `emerge --info |
111 |
'=www-client/chromium-104.0.5110.0::gentoo'`, |
112 |
* the complete build log and the output of `emerge -pqv |
113 |
'=www-client/chromium-104.0.5110.0::gentoo'`. |
114 |
* The complete build log is located at |
115 |
'/var/tmp/portage/www-client/chromium-104.0.5110.0/temp/build.log'. |
116 |
* The ebuild environment file is located at |
117 |
'/var/tmp/portage/www-client/chromium-104.0.5110.0/temp/die.env'. |
118 |
* Working directory: |
119 |
'/var/tmp/portage/www-client/chromium-104.0.5110.0/empty' |
120 |
* S: |
121 |
'/var/tmp/portage/www-client/chromium-104.0.5110.0/work/chromium-104.0.5110.0' |
122 |
>>> Failed to emerge www-client/chromium-104.0.5110.0, Log file: |
123 |
########################## |
124 |
|
125 |
|
126 |
Slot conflict??? |
127 |
|
128 |
No problem! I'll just go to eselect and pick a different slot......... |
129 |
|
130 |
|
131 |
Oh wait, that was the OLD way of selecting slots... I went searching for |
132 |
an explanation for how to set it up and it was like: |
133 |
|
134 |
|
135 |
shifty informant: "Well you are supposed to go to the alley behind the |
136 |
tavern?" |
137 |
|
138 |
Me: "Which tavern?" |
139 |
|
140 |
shifty informant: "You know *the* tavern... You go there between |
141 |
midnight and 3 AM and when you are confronted you make the sign." |
142 |
|
143 |
Me: "What sign, how am I supposed to make the sign?" |
144 |
|
145 |
shifty informant: "You know, the sign, every thief knows how to make |
146 |
it..." |
147 |
|
148 |
Me: [ starts to say I'm not a thief then gives up..] |
149 |
|
150 |
shifty informant: When you get inside the club just show off your dagger |
151 |
throwing skills and then they'll give you the line you need to put in |
152 |
the file to make it work." |
153 |
|
154 |
Me: I don't even own a dagger.... Wait, file?!?!? WHAT FILE??? WHERE |
155 |
IS THIS FILE??? WHY DO i HAVE TO EDIT IT?? WHERE DID YOU RUN OFF TO??? |
156 |
WHO DO I TALK TO TO GET SOME REAL INFORMATION??? |
157 |
|
158 |
|
159 |
|
160 |
KDE will keep me busy the rest of the night, I only use a handful of its |
161 |
utilities and don't even know how to set it up as a window manager but |
162 |
it likes to version bump its packages several times an hour and cause |
163 |
emerge conflicts just to piss me off... |
164 |
|
165 |
-- |
166 |
Beware of Zombies. =O |
167 |
#EggCrisis #BlackWinter |
168 |
White is the new Kulak. |
169 |
Powers are not rights. |