1 |
Hemmann, Volker Armin wrote: |
2 |
> On Saturday 27 May 2006 19:58, Alexander Skwar wrote: |
3 |
>> Richard Fish wrote: |
4 |
>> > On 5/27/06, Alexander Skwar <listen@×××××××××××××××.name> wrote: |
5 |
>> >> gcc update "Nothing needs to be done".... Sure... How much did the |
6 |
>> >> person who wrote this check? "Hello World!" worked, and that's it? |
7 |
>> >> |
8 |
>> >> Sometimes this complete lack of QA is really pissing me off :( |
9 |
>> > |
10 |
>> > Stop using ~arch packages, or stop whining. |
11 |
>> |
12 |
>> No, I won't do neither. The GWN and the upgrade doc used to say, |
13 |
>> that an upgrade is (basically) riskless. |
14 |
> |
15 |
> no it does not. |
16 |
|
17 |
Yes, it does. |
18 |
|
19 |
> You are talking bullshit. |
20 |
|
21 |
Am I? |
22 |
|
23 |
> GWN: |
24 |
> |
25 |
> The number of applications that do not compile with gcc-4.1 is extremely small |
26 |
> now, and most users should not experience any problems with ~arch packages |
27 |
> not compiling. |
28 |
|
29 |
Yes, read it. I'm not complaining about packages which do not compile because |
30 |
of gcc 4.1.1. I complained because KDE stopped working. I complained, because |
31 |
I had to re-compile glibc, so that I could compile glib. |
32 |
|
33 |
So, please YOU read again. |
34 |
|
35 |
> Read it, understand it. It is hard, I know. But it does not say 'riskless'. |
36 |
> Not even 'basically riskless'. Read again. |
37 |
|
38 |
Yes, please do so - please read again. Make note of the sentence right |
39 |
before the sentence, which you've quoted: |
40 |
|
41 |
| The upgrade should be incredibly easy and require no additional work to |
42 |
| install and use. |
43 |
|
44 |
If that's not "basically riskless", then I don't know what basically riskless is. |
45 |
|
46 |
> And the uzpgrade guide says: |
47 |
|
48 |
The upgrade doc used to say, that upgrading from 3.4.x to 4.1.1 will be |
49 |
painless (I don't know the exact words anymore, as the box has been |
50 |
thankfully removed, which is VERY good). |
51 |
|
52 |
> Generally speaking, upgrades to bug fix releases, like from 3.3.5 to 3.3.6, |
53 |
> should be quite safe -- just emerge new version, switch your system to use it |
54 |
> and rebuild the only affected package, libtool. However, some GCC upgrades |
55 |
> break binary compatibility; |
56 |
|
57 |
And it said, that 4.1.1 was supposed to be binary compatible to 3.4.6. |
58 |
|
59 |
> in such cases a rebuild of the affected packages |
60 |
> (or even whole toolchain and system) might be required. |
61 |
|
62 |
And thus, a rebuild of world/tc/system wouldn't be required. |
63 |
|
64 |
>> > ~arch works most of the |
65 |
>> > time, but it is a _testing_ branch. Do you expect the devs to login |
66 |
>> > to each and every Gentoo user's system to test a new package and |
67 |
>> > ensure complete functionality before adding it to ~arch? |
68 |
>> |
69 |
>> Bullshit. |
70 |
>> |
71 |
>> I'd expect them to do testing and not give so bold statements |
72 |
>> as "The upgrade should be incredibly easy and require no additional |
73 |
>> work to install and use. " without making VERY sure, that this |
74 |
>> is actually true. |
75 |
>> |
76 |
> |
77 |
> and ~arch is the testing ground. Basic testing 'it works or it works not' are |
78 |
> the hard-masked packages. |
79 |
|
80 |
I guess we'll disagree about the level of "basic testing". IMO there should |
81 |
be different levels for ordinary packages (say net-mail/safecat) and rather |
82 |
low level system packages like gcc, glibc - and maybe everything in the sys-* |
83 |
categories. |
84 |
|
85 |
> Maybe you should calm down? |
86 |
|
87 |
I am calm. Just don't tell me, that everything's fine, when it actually |
88 |
isn't. |
89 |
|
90 |
>> Did you yet re-compile Qt 3 and Qt 4? No? |
91 |
>> |
92 |
>> Then you're experiences just don't count. KDE broke on my |
93 |
>> system, when I recompiled Qt. Before the recompile, KDE was fine. |
94 |
>> As I've wrote in lengths on the bug report. Seems you've not read |
95 |
>> it - why not? Why am I writing reports and *also* post links |
96 |
>> here? |
97 |
> |
98 |
> oh, that is sooo surprising. |
99 |
|
100 |
Yes, it is, isn't it? |
101 |
|
102 |
> Most of the times, a qt-update requires |
103 |
> recompiling kdelibs, base and network (and kdepim). |
104 |
|
105 |
Where was there a Qt update? |
106 |
|
107 |
So, thanks for agreeing with me |
108 |
|
109 |
> Something that happens |
110 |
> even without gcc-updates. |
111 |
|
112 |
No, it doesn't. |
113 |
|
114 |
>> Did you try to compile glib? No? Then I guess you've done no testing. |
115 |
> |
116 |
> if he does not have glib? |
117 |
|
118 |
Then he installs it. |
119 |
|
120 |
>> Or what kind of testing have you done? |
121 |
> |
122 |
> enough for his system? |
123 |
|
124 |
Not enough to experience the errors which have been reported here. |
125 |
|
126 |
>> > Since these are all heavy |
127 |
>> > C++ users, I am sure that for my (pure ~x86) system, there are no |
128 |
>> > issues. |
129 |
>> |
130 |
>> Congrats. It's not only me who's having problems. |
131 |
>> |
132 |
> |
133 |
> no, you are not the only one, but you are one who makes a lot of fuss about |
134 |
> problems, that are easy to solve |
135 |
|
136 |
Pardon, but an "emerge -e world" is not easy to solve. Sure, it's not |
137 |
that hard, but it takes so very long and because of that, it's to be |
138 |
avoided like the plague. |
139 |
|
140 |
And also pardon me, when I'm annoyed because of too bold statements |
141 |
which turn out to be wrong. If it says "no problems expected", then |
142 |
that's what I expect. I don't expect to run into deep problems. And |
143 |
the GWN and upgrade doc clearly stated, that there were no problems |
144 |
to be expected. |
145 |
|
146 |
Heck - the GWN still says so. You should just read it yourself. Or |
147 |
let me read it to you: |
148 |
|
149 |
| The upgrade should be incredibly easy and require no additional |
150 |
| work to install and use. The number of applications that do not |
151 |
| compile with gcc-4.1 is extremely small now, and most users should |
152 |
| not experience any problems with ~arch packages not compiling. |
153 |
|
154 |
So, "emerge -e world" is "no additional work" for you? Well, guess |
155 |
we've got differing oppinions in this case then. |
156 |
|
157 |
> and even happen without any gcc updates - |
158 |
|
159 |
Those problems? Seldom. |
160 |
|
161 |
> and you should have learnt to deal with a long time ago. |
162 |
|
163 |
I deal with them just fine. |
164 |
|
165 |
Alexander Skwar |
166 |
-- |
167 |
Economists are still trying to figure out why the girls with the least |
168 |
principle draw the most interest. |
169 |
-- |
170 |
gentoo-user@g.o mailing list |