| 1 |
> |
| 2 |
> |
| 3 |
>>emm, is not -uD something almost everybody does, but nobody should do? |
| 4 |
>> |
| 5 |
>>I had the same error - AFAIR reemerging java-config solved it. |
| 6 |
>> |
| 7 |
>> |
| 8 |
|
| 9 |
No, -uD is update deep, -UD is what you should NOT be doing. the U |
| 10 |
means update only. The difference is if say package-1.45 was marked |
| 11 |
stable and then found to be buggy, it gets masked in some way. Then |
| 12 |
package-1.44 would be the most current stable package. The U flag says |
| 13 |
not to go back to the 1.44 package. On the other hand, the -u flag will |
| 14 |
"upgrade" to an older package if it is currently the newest unmasked or |
| 15 |
stable package. |
| 16 |
|
| 17 |
I think the biggest problem, I could be wrong thoug, is that usually |
| 18 |
when packages get remasked like that and upgrades go backwards, it is a |
| 19 |
security problem. And even that seems to be uncommon. I have not ever |
| 20 |
seen one of my packages go backwards but I could have missed one or two. |
| 21 |
-- |
| 22 |
gentoo-amd64@g.o mailing list |
Archives