On 2018-07-06, Grant Edwards wrote:
> On 2018-07-06, Grant Edwards wrote:
>
>> Now that the public key stuff is working again (knock on wood), I'm
>> curious if it's usual for an emerge --sync to take 10-15 minutes
>> longer than it used due to the "Verifying /usr/portage" step.
>>
>> On some
Rich Freeman wrote:
> On Fri, Jul 6, 2018 at 4:43 PM Grant Edwards
> wrote:
>> On 2018-07-06, Grant Edwards wrote:
>>
>>> Now that the public key stuff is working again (knock on wood), I'm
>>> curious if it's usual for an emerge --sync to take 10-15 minutes
>>> longer than it used due to the
On Fri, Jul 6, 2018 at 4:43 PM Grant Edwards wrote:
>
> On 2018-07-06, Grant Edwards wrote:
>
> > Now that the public key stuff is working again (knock on wood), I'm
> > curious if it's usual for an emerge --sync to take 10-15 minutes
> > longer than it used due to the "Verifying /usr/portage"
On Friday, 6 July 2018 21:43:35 BST Grant Edwards wrote:
> On 2018-07-06, Grant Edwards wrote:
> > Now that the public key stuff is working again (knock on wood), I'm
> > curious if it's usual for an emerge --sync to take 10-15 minutes
> > longer than it used due to the "Verifying /usr/portage"
On 2018-07-06, Grant Edwards wrote:
> Now that the public key stuff is working again (knock on wood), I'm
> curious if it's usual for an emerge --sync to take 10-15 minutes
> longer than it used due to the "Verifying /usr/portage" step.
>
> On some systems (with fewer packages installed) it only
On 2018-07-06, Dale wrote:
> I haven't timed mine yet but that sounds about like mine here. I'm not
> sure what the bottleneck is but I have a four core AMD CPU running at
> 3.2GHz with 16GBs of ram and SATA spinning rust drives. While I'm glad
> to have the added security measures, it does
6 matches
Mail list logo
