Have you added an overlay using layman?
Gentoo's List : https://overlays.gentoo.org/
Add : layman -a
Sync : layman -S
I use the Palemoon overlay :
/var/lib/layman/palemoon/profiles/repo_name
contents of repo_name :
palemoon
When you add the overlay the directories and files are created in
/va
On Thu, 7 Mar 2019 17:52:08 -0600, Dale wrote:
> >> It seems you can change the output of wget with the --progress
> >> option, which you would set in FETCHCOMMAND in make.conf.
> > Doh! I thought that the output format looked familiar: I didn't
> > realize it was using wget. Thanks...
> >
Grant Edwards wrote:
> On 2019-03-07, Neil Bothwick wrote:
>> On Thu, 7 Mar 2019 20:01:46 - (UTC), Grant Edwards wrote:
>>
>>> I've noticed that when downloading large files, emerge seems to write
>>> an excessive number of lines to /var/log/emerge-fetch.log. The last
>>> time I looked, it wa
On 2019-03-07, Neil Bothwick wrote:
> On Thu, 7 Mar 2019 20:01:46 - (UTC), Grant Edwards wrote:
>
>> I've noticed that when downloading large files, emerge seems to write
>> an excessive number of lines to /var/log/emerge-fetch.log. The last
>> time I looked, it was writing 30-40 lines/second
On Thu, 7 Mar 2019 20:01:46 - (UTC), Grant Edwards wrote:
> I've noticed that when downloading large files, emerge seems to write
> an excessive number of lines to /var/log/emerge-fetch.log. The last
> time I looked, it was writing 30-40 lines/second while downloading.
>
> Is there any way t
I've set up layman, and it appears to work, but I seem to be missing a
config entry somewhere. Whenever I run emerge I get...
=
WARNING: One or more repositories have missing repo_name entries:
/var/lib/layman/profiles/rep
I've noticed that when downloading large files, emerge seems to write
an excessive number of lines to /var/log/emerge-fetch.log. The last
time I looked, it was writing 30-40 lines/second while downloading.
Is there any way to reduce that to a saner number? I don't really see
the point of updatin
Mick wrote :
> I can't recall the OP mentioning corrupt data, which is
> usually the first thing observed with faulty memory.
I did, actually, last Friday. Numbers of files in the portage tree suddenly
changed owner (or group), and when I fixed that git complained that my numerous
local change
Grant Edwards wrote :
> Perhaps it's already been mentioned, but failing RAM can cause all
> sorts failures that might appear to be failing disks, failing network
> cards, failing video cards whatever. I'd run memtest86 for at least
> 12 hours just to make sure...
Good idea. I'll try that.
--
Mick wrote:
> On Wednesday, 6 March 2019 03:15:14 GMT Michael Cook wrote:
>> On 3/5/19 8:34 PM, Philip Webb wrote:
>>> 190305 Michael Cook wrote:
On 3/5/19 7:47 PM, Dale wrote:
> I just did a KDE plasma upgrade to 5.15. I ran into a slight problem
> that may or may not affect others s
Mick wrote:
>
> I can think of 3 things, but more learned M/L contributors may add to these:
>
> 1. The SATA connection has come loose. With time and movement it can come
> (slightly) adrift. Pushing it back in fully fixes this problem - also see No.
> 2 below.
>
> 2. The physical connector's co
On Thursday, 7 March 2019 14:45:31 GMT Rich Freeman wrote:
> On Thu, Mar 7, 2019 at 9:29 AM Grant Edwards
wrote:
> > On 2019-03-07, Mick wrote:
> > > I can think of 3 things, but more learned M/L contributors may add to
> > > these:
> > >
> > > 1. The SATA connection has come loose. With time
On Thu, Mar 7, 2019 at 9:29 AM Grant Edwards wrote:
>
> On 2019-03-07, Mick wrote:
>
> > I can think of 3 things, but more learned M/L contributors may add to these:
> >
> > 1. The SATA connection has come loose. With time and movement it can come
> > (slightly) adrift. Pushing it back in fully
On 2019-03-07, Mick wrote:
> I can think of 3 things, but more learned M/L contributors may add to these:
>
> 1. The SATA connection has come loose. With time and movement it can come
> (slightly) adrift. Pushing it back in fully fixes this problem - also see No.
> 2 below.
>
> 2. The physical
On Thursday, 7 March 2019 10:10:53 GMT Peter Humphrey wrote:
> On Wednesday, 6 March 2019 16:31:27 GMT Laurence Perkins wrote:
> > On Fri, 2019-03-01 at 10:12 +, Peter Humphrey wrote:
> > > [OT]
> > > Evidence is mounting that the Atom box is in terminal decline. I get
> > > things like batches
On Wednesday, 6 March 2019 16:31:27 GMT Laurence Perkins wrote:
> On Fri, 2019-03-01 at 10:12 +, Peter Humphrey wrote:
> > [OT]
> > Evidence is mounting that the Atom box is in terminal decline. I get
> > things like batches of files in the portage tree changing owner, and then
> > when I corr
16 matches
Mail list logo
