Christopher Sawtell wrote:
> On Wednesday 11 April 2007 10:56:40 Benedikt Boehm wrote:
>> ... don't care about an uber-vision or direction and just keep your
>> friggin packages alive and working?
> Indeed!!
>
> Doing an emerge --deep --update world last week b0rked updating about a
> couple
Matthias Langer wrote:
>
> Well, I don't know what your problem really is about; I'm running x86,
> and if something breaks on my system, it's mostly not because of broken
> packages, but because I should have been informed about possible issues
> that could have been caused by an upgrade, and how
On Wed, 2007-04-11 at 13:26 +1200, Christopher Sawtell wrote:
> On Wednesday 11 April 2007 10:56:40 Benedikt Boehm wrote:
> > ... don't care about an uber-vision or direction and just keep your
> > friggin packages alive and working?
> Indeed!!
>
> Doing an emerge --deep --update world last we
On 4/10/07, Christopher Sawtell <[EMAIL PROTECTED]> wrote:
Evenutally I realized that the problem was
gcc-4.1.2 had a supposedly executable file filled with zeros in its
file-set. Masking gcc-4.1.2 and reverting to the 4.1.1 series has nearly
got me going again.There is still one package which wo
On Wednesday 11 April 2007 10:56:40 Benedikt Boehm wrote:
> ... don't care about an uber-vision or direction and just keep your
> friggin packages alive and working?
Indeed!!
Doing an emerge --deep --update world last week b0rked updating about a
couple of dozen packages. Evenutally I realize
... don't care about an uber-vision or direction and just keep your
friggin packages alive and working?
I'm so sick to hear people crying that noone is around to tell them what
to do..
So here is my proposal:
ABSTAIN!
That's it for now :)
--
gentoo-dev@gentoo.org mailing list
