Am 16.08.2011 02:18, schrieb Dale:
> Sebastian Beßler wrote:
>>
>> But why was autounmask=y complaining but not autounmask=n?
>> The dependency of the virtual was missing both times so shouldn't emerge
>> spit some error out both times?
>>
>> Greetings
>>
>> Sebastian
>>
>>    
> 
> Because autounmask=n assumes you don't want to upgrade anything that is
> masked so it didn't suggest it.

But there was a broken dependency, not just something that could be
upgraded. autounmask=y now, after setting the virtual to -~amd64 too, is
quiet and doesn't tells me to unmask anything.

Still think that emerge should have thrown an error both times, but if
it is ok for anyone here that it doesn't then it is ok for me too ;-)

> Ain't life confusing?

Yes, yes it is!