1 |
On Saturday, 30 January 2021 09:37:57 GMT Alan Grimes wrote: |
2 |
> I'm not actually talking about the communist takeover of the planet, I |
3 |
> mean I'm looking at what this brokenest version of portage EVER is not |
4 |
> doing... |
5 |
> |
6 |
> I mean I always update my portage first thing after sync, because that's |
7 |
> what you do, RIIIIIGHT???? |
8 |
|
9 |
Not RIIIIIGHT. |
10 |
|
11 |
I let portage decide when it needs to update itself, after it has decided |
12 |
which of its dependencies it may need to update first. |
13 |
|
14 |
When I'm driving a car with an automatic gearbox I don't start changing gears |
15 |
myself, unless something breaks and I *have* to. |
16 |
|
17 |
|
18 |
> I know you hate my scripts but they have a 15 year track record. =| |
19 |
|
20 |
I'd leave others to comment on the suitability of your loop-a-loop scripts, |
21 |
which often tie themselves up in a knot and typically result in your moaning |
22 |
posts on this M/L. |
23 |
|
24 |
|
25 |
> On one terminal I have this bullshit going on, at this pace it will take |
26 |
> longer than my natural lifespan to clear this nonsense: |
27 |
> ###################### |
28 |
> |
29 |
> tortoise ~ # ./pretendupdate |
30 |
> |
31 |
> These are the packages that would be merged, in order: |
32 |
> |
33 |
> Calculating dependencies... done! |
34 |
> |
35 |
> |
36 |
> [ebuild R ] app-officeext/sun-templates-1.0.0-r1::gentoo |
37 |
> OFFICE_IMPLEMENTATION="libreoffice (-openoffice%)" 0 KiB |
38 |
> [ebuild U ] app-office/libreoffice-7.0.4.2::gentoo |
39 |
> [6.4.7.2::gentoo] USE="branding clang%* cups custom-cflags%* dbus |
40 |
> gstreamer gtk java mariadb vulkan%* -accessibility -base -bluetooth |
41 |
> -coinmp -debug -eds -firebird -googledrive -kde -ldap -odk -pdfimport |
42 |
> -postgres -test" LIBREOFFICE_EXTENSIONS="-nlpsolver -scripting-beanshell |
43 |
> -scripting-javascript -wiki-publisher" PYTHON_SINGLE_TARGET="python3_8* |
44 |
> -python3_7* -python3_9 (-python3_6%)" 347,325 KiB |
45 |
> [ebuild N ] dev-java/openjdk-11.0.9_p11:11::gentoo USE="alsa |
46 |
> cups jbootstrap pch -debug -doc -examples (-gentoo-vm) -headless-awt |
47 |
> -javafx (-selinux) -source -systemtap" 89,491 KiB |
48 |
> |
49 |
> Total: 3 packages (1 upgrade, 1 new, 1 reinstall), Size of downloads: |
50 |
> 436,815 KiB |
51 |
> |
52 |
> * Error: circular dependencies: |
53 |
> |
54 |
> (dev-java/openjdk-11.0.9_p11:11/11::gentoo, ebuild scheduled for merge) |
55 |
> depends on |
56 |
> (dev-java/openjdk-11.0.9_p11:11/11::gentoo, ebuild scheduled for merge) |
57 |
> (buildtime) |
58 |
> |
59 |
> * Note that circular dependencies can often be avoided by temporarily |
60 |
> * disabling USE flags that trigger optional dependencies. |
61 |
|
62 |
|
63 |
Did you try removing the java USE flag from app-office/libreoffice as emerge |
64 |
suggests above to see if it proceeds? |
65 |
|
66 |
Alternatively, you could unmerge dev-java/openjdk and see what portage wants |
67 |
to bring in. |
68 |
|
69 |
Using '--depclean -p -v' on dev-java/openjdk before you unmerge it will show |
70 |
you what else could break. |
71 |
|
72 |
|
73 |
> !!! Multiple package instances within a single package slot have been pulled |
74 |
> !!! into the dependency graph, resulting in a slot conflict: |
75 |
> |
76 |
> dev-lang/perl:0 |
77 |
> |
78 |
> (dev-lang/perl-5.32.0-r1:0/5.32::gentoo, ebuild scheduled for merge) |
79 |
> USE="berkdb gdbm ithreads -debug -doc -minimal" ABI_X86="(64)" pulled in by |
80 |
> =dev-lang/perl-5.32* required by |
81 |
> (virtual/perl-XSLoader-0.300.0-r3:0/0::gentoo, installed) USE="" |
82 |
> ABI_X86="(64)" |
83 |
> ^ |
84 |
> ^^^^^ |
85 |
|
86 |
Perhaps a run of 'perl-cleaner --reallyall' is in order before you proceed. |
87 |
|
88 |
|
89 |
> (and 46 more with the same problem) |
90 |
[... snip] |
91 |
|
92 |
> Notice, it's only giving me ONE package at a time to remove, it takes |
93 |
> about 10 minutes to get through a cycle of this nonsense. Wait a minute, |
94 |
> what kind of bullshit is this "--verbose conflicts" faggotry? why isn't |
95 |
> it the default and impossible to disable???? I mean that would have |
96 |
> saved me hours today... I've been putting out all kinds of fires on |
97 |
> this turd sandwitch of a distro since I decided to update today. |
98 |
|
99 |
Doing it manually, one package at a time is a rather long winded approach. |
100 |
Using perl-cleaner is better and easier in this case. |
101 |
|
102 |
|
103 |
> fuckit, I'm adding this shit to the goddamned, cock-sucking make.conf |
104 |
> and there's nothing you can do to stop me!!! Why for fuck's sake do I |
105 |
> have to fix this shit at 4:30 am and can't get it all done in the middle |
106 |
> of the afternoon when I started??? |
107 |
|
108 |
Enjoying a self-induced crisis of tourettes at 4:30 am is your prerogative. |
109 |
Using portage and associated tools the way devs intended should bring more |
110 |
satisfactory results. |
111 |
|
112 |
|
113 |
> Why am I required to manually update a dozen config files just to get |
114 |
> things moving each time I do this?? Is it really impossible to just keep |
115 |
> doing what I set up last time?, you know the time when I stopped messing |
116 |
> with it because it was working??? |
117 |
> |
118 |
> |
119 |
> Do you have any idea how broken it is right now? It will look like it's |
120 |
> emerging stuff, then start no processes, decompress any files, compile |
121 |
> any code, or anything, just tick through as if it were working very very |
122 |
> very slowly but not actually do anything... |
123 |
> |
124 |
> So this version of portage is the first one I've seen that is literally |
125 |
> incapable of emerging a pacakge! Unbelievable, a package manager |
126 |
> incapable of performing its primary function... |
127 |
> |
128 |
> I have no idea how I'm going to fix this mess this time, I'm going to |
129 |
> have to mask the current version of portage and get a binary of one that |
130 |
> is capable of emerging and put that in. |
131 |
> |
132 |
> How did you break it this bad, HOW???? |
133 |
> |
134 |
> All you had to do was nothing and it would still be working!!! |
135 |
|
136 |
Your particular approach to managing your system(s) tends to arrive at similar |
137 |
unhappy results. There is a pattern here and on this M/L it is an outlier. |
138 |
You could modify your approach to improve the results, or you could carry on |
139 |
repeating the same thing and somehow retain an expectation of a different |
140 |
outcome. This is not an ad hominem criticism, just my observation on your |
141 |
approach. I'm not saying portage is the best thing since sliced bread. |
142 |
However, using it as intended works most of the time for most of the people. |