1 |
Alan Grimes wrote: |
2 |
> Gregory Woodbury wrote: |
3 |
>> |
4 |
>> On Sat, May 28, 2016 at 4:53 PM, Neil Bothwick <neil@××××××××××.uk |
5 |
>> <mailto:neil@××××××××××.uk>> wrote: |
6 |
>> |
7 |
>> On Sat, 28 May 2016 21:54:09 +0200, Volker Armin Hemmann wrote: |
8 |
>> |
9 |
>> > thanks a lot. My eyes are bleeding. |
10 |
>> |
11 |
>> Serves you right for being daft enough to read it again! |
12 |
>> |
13 |
>> I'd suggest that Alan RTFM for the commands he uses, but that |
14 |
>> would be a |
15 |
>> waste of keystrokes. |
16 |
>> |
17 |
>> |
18 |
>> I have to agree with ng0 |
19 |
>> |
20 |
>> WOW! |
21 |
>> |
22 |
>> Alan just wants to start it and walk away, as if Gentoo was a binary |
23 |
>> distribution |
24 |
>> that handles it all upstream. He doesn't want to take the time to |
25 |
>> review what |
26 |
>> emerge is proposing and see if changes are needed first. |
27 |
> You know what? fuck you. That's what. |
28 |
> |
29 |
> The update list it's proposing is 403 packages, or roughly 25% of my |
30 |
> system. |
31 |
> |
32 |
> Packages are being updated at such a breakneck pace these days that it |
33 |
> simply isn't humanly possible to review these manually, or even do |
34 |
> anything intelligent if I tried. Back in the golden age, for about ten |
35 |
> years even! my approach to updating my system worked great. Then emerge |
36 |
> got ornery and stopped letting the necessary, cathartic, inevitable, |
37 |
> trainwreck take place, which is actually a good thing because the |
38 |
> partial-good, update which seems nightmarish on first analysis, |
39 |
> ***ACTUALLY CORRECTS ITSELF WHEN THE SCRIPT IS RUN REPEATEDLY UNTIL NO |
40 |
> PROBLEMS REMAIN AND THE SYSTEM IS PRISTINE AND GOOD FOR REBOOT***. I |
41 |
> have done this happily many many many many times. It actually works that |
42 |
> way and I was gleefully singing gentoo's praise for many years. |
43 |
> |
44 |
> No, the penguins seem to think it is possible to get it perfect on the |
45 |
> first iteration. It's not. It's not just that there are a handful of |
46 |
> packages that just won't work no matter what, it's just that it is |
47 |
> sometimes necessary to let a bootstrapping process take place. This |
48 |
> actually works if you don't use such draconian checking. |
49 |
|
50 |
So, you still think it is emerge that is the problem and not your script |
51 |
which everyone that has seen it says is the wrong way to do a update? ROFL |
52 |
|
53 |
I did a emerge -e world not to long ago. Out of the over 1,000 |
54 |
packages on here, I only had one failure. Just one. |
55 |
|
56 |
>> Hey Alan: Gentoo is NOT a start an update and walk away setup. Some human |
57 |
>> mind needs to be involved if troubles arise. Also, read make.conf(5) |
58 |
>> and set up |
59 |
>> the various variables correctly; PYTHON_SINGLE_TARGET should only have |
60 |
>> one python version set. |
61 |
> DO YOU SERIOUSLY THINK I'M THAT STUPID??? SERIOUSLY???? |
62 |
|
63 |
Do you really want a answer to that? Seriously? You asked so I guess |
64 |
you do. Here it is. Yes! lol The way you do things, and continue to |
65 |
do things, even after having several VERY experienced users tell you |
66 |
that the way you are doing things is wrong pretty much says it all. If |
67 |
I post that I was doing something and getting a bad result and someone |
68 |
such as Neil and/or Alan McKinnon tells me I am doing it wrong, you can |
69 |
bet your last dollar that I am about to change how I do things. Why, if |
70 |
either or both of them tell me I am doing something wrong, I'm doing it |
71 |
wrong. If I continue to do things the same way, well, that would be my |
72 |
fault not members of this list or emerge/portage. So far, I don't |
73 |
recall seeing a single post that supports how your script is set up. |
74 |
Not one, except you of course. |
75 |
|
76 |
> |
77 |
>> Furthermore, the current portage doesn't require the revdep-rebuild |
78 |
>> step because |
79 |
>> of the @preserved-rebuild set creation. |
80 |
> That missfeature is incompatible with how I use my system. I have not |
81 |
> reformatted my hard drive in six years. |
82 |
> |
83 |
> The principle way I accomplish that is by prohibiting the growth of |
84 |
> cruft in the system. I cannot tolerate the accumulation of back versions |
85 |
> anywhere in the system except where absolutely necessary. So if it is |
86 |
> possible to re-build broken packages against new versions, I demand that |
87 |
> take place |
88 |
> as quickly as possible such that the system is left in the most pristine |
89 |
> and self-consistent state possible. --- secret of immortality, dude. =\ |
90 |
> |
91 |
> Gentoo used to be superlatively excellent at that. |
92 |
> |
93 |
>> In any case, to try and force things through without looking at what |
94 |
>> problems are occuring |
95 |
>> is just (excuse my language) batshit crazy stupid. |
96 |
> You |
97 |
> dumb. |
98 |
> shit. |
99 |
> |
100 |
> You literally have no fucking clue do you? |
101 |
|
102 |
Thing is, it would seem to me that others on this list do have a clue |
103 |
and have tried several times to explain that to you. The person who |
104 |
doesn't have a clue is the one that comes here complaining about |
105 |
problems that no one else here has. |
106 |
|
107 |
|
108 |
> |
109 |
> Do you think I enabled that missfeature they introduced a few years ago |
110 |
> that hid all of the build output so all I got to see was |
111 |
> |
112 |
> installing package (1/400) |
113 |
> installing package (2/400) |
114 |
> installing package (3/400) |
115 |
> |
116 |
> I am typing this on my smaller monitor because I have the full verbose |
117 |
> build process fullscreen on my 24". That's right, for the last 12 years, |
118 |
> I have watched every single build take place in live time because I've |
119 |
> watched it execute every single compiler invocation, I have watched |
120 |
> every error and warning message. |
121 |
> |
122 |
> I do not need log files because I watch everything in live time. By |
123 |
> doing this, I have learned things about my packages that you fucking |
124 |
> dipshits couldn't imagine. Back before when Gentoo jumped the shark |
125 |
> (tried to force everyone onto libav), the system was completely |
126 |
> self-correcting, If the system set was intact, literally every other |
127 |
> problem would self correct. I didn't need to rant on this list because |
128 |
> everything was perfect. |
129 |
> |
130 |
> The problem is that the portage people don't understand how the packages |
131 |
> actually work or what happens when these stupid, recently implemented |
132 |
> checks are disabled and emerge is run iteratively. |
133 |
> |
134 |
|
135 |
Here's a idea. Since YOU are the only one having this problem, why |
136 |
don't YOU change what you are doing to something that actually works? |
137 |
What you are doing doesn't work. Try something else. Funny how those |
138 |
"stupid" checks work for everyone else. |
139 |
|
140 |
|
141 |
>> I use my update generator script so make the emerge command(s) just so |
142 |
>> I can preview the packages and modify the sequences or leave out some |
143 |
>> updates |
144 |
>> if i need/want to do so. (E.g. I may want to defer a chromium or |
145 |
>> libreoffice update |
146 |
>> to after other updates are done and/or set them to occur with a lower |
147 |
>> niceness or |
148 |
>> an ionice idle class.) |
149 |
> It wouldn't let me do that because it was throwing a conflict message |
150 |
> for libreoffice so I was forced to temporarily uninstall it to clear a |
151 |
> block message, fuck you again portage... |
152 |
> |
153 |
> |
154 |
|
155 |
Sure. |
156 |
|
157 |
May I suggest something. If you want to automate the upgrade process, |
158 |
why don't you ask for others to post how THEY do their updates? Your |
159 |
way is a disaster and it won't get any better until YOU change what you |
160 |
are doing. When I run into a problem, I ask for help and then others |
161 |
give me ideas on how to do things better. I been using Gentoo since |
162 |
about 2003. I've hit the occasional bump in the road but the way you do |
163 |
things, it's just not going to work. Ask anyone here, I can run into |
164 |
some strange things at times but my process works about 99% of the |
165 |
time. It does so because over the years I have found the method that |
166 |
works best. More importantly, I've adapted to what emerge/portage |
167 |
expects from me. |
168 |
|
169 |
I mentioned this before. If you keep posting but then refuse to accept |
170 |
help, people will start ignoring or blocking your messages. Based on |
171 |
the posts that I see, I suspect some may have already. At some point, |
172 |
even I will. I've only ever blocked one other person on this list. I |
173 |
can see that doubling at some point because you don't come here for help |
174 |
or accept any when it is given. You just come here to gripe about |
175 |
things not working like you want when it is your method that is broken. |
176 |
|
177 |
Either change how you do things or expect to keep running into the same |
178 |
problems you are now. If you don't change, neither will what you get |
179 |
from portage/emerge. This is about as nice as I know how to put it. |
180 |
|
181 |
Dale |
182 |
|
183 |
:-) :-) |