On Wednesday 08 Jan 2014 12:31:52 I wrote:
> I'm having a similar problem on my local LAN server, an Atom box. I sync
> daily, and I've just synced again to make sure (31000 files, yet again,
> nearly all in metadata).
>
> The Atom's packages directory is NFS-mounted in a 32-bit chroot on my
> wor
On Monday 06 Jan 2014 21:35:41 Alan McKinnon wrote:
> On 06/01/2014 19:58, »Q« wrote:
> > I had exactly the same weirdness after 1.6.8 was stabilized. I waited
> > a few hours, re-synced the tree, and then updated without any warnings
> > about blocks; the old libpng was unmerged and 1.6.8 was m
On 06/01/2014 19:58, »Q« wrote:
> On Sun, 5 Jan 2014 15:57:10 +
> 张东亚 wrote:
>
>> Hi list,
>>
>> When I do a world upgrade, I have encountered the following slot
>> conflict:
>>
>>
>> media-libs/libpng:0
>>
>> (media-libs/libpng-1.5.17-r1::gentoo, installed) pulled in by
>> media-libs/l
On Sun, 5 Jan 2014 15:57:10 +
张东亚 wrote:
> Hi list,
>
> When I do a world upgrade, I have encountered the following slot
> conflict:
>
>
> media-libs/libpng:0
>
> (media-libs/libpng-1.5.17-r1::gentoo, installed) pulled in by
> media-libs/libpng:0/0= required by
> (dev-python/wxpytho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
econti wrote:
> Hi all
> I am a bit confused :-(
> I upgrade my box weekly. After the last upgrade the "emerge -NDpvu" gave
> me the output you can see in the attached up_20091010 file.
> As you can see there were a lot packages to upgrade with a lot o
5 matches
Mail list logo
