Rich Freeman wrote:
> On Mon, Aug 3, 2020 at 8:24 AM Dale wrote:
>> In the past, I've never seen the drive on the larger files be that slow even
>> toward the end. Generally, it stays pretty close to 180MBs/sec or so which
>> is what I usually get with PMR drives.
> Yeah, just hard to be
Andrey F. wrote:
> Can you reproduce by manually curling it?
>
I had to look up curl to see if I even have it installed. I've seen it
mentioned but no idea what it is but it is installed here. I'm not
worried about the server that was slow since I removed it. I think it
was easylist or
On Monday, 3 August 2020 20:15:45 BST Rich Freeman wrote:
> On Mon, Aug 3, 2020 at 3:01 PM Peter Humphrey wrote:
> > On Monday, 3 August 2020 14:18:22 BST Rich Freeman wrote:
> > > Sounds like you want --usepkgonly y --binpkg-respect-use y (the first
> > > is the same as -K). At least, I think
Anybody know more? Found a Qubes bug,
https://github.com/QubesOS/qubes-issues/issues/5416. Reproduced below is the
output from an attempted modprobe amdgpu.
[ 338.377745] fb0: switching to amdgpudrmfb from EFI VGA
[ 338.377842] Console: switching to colour dummy device 80x25
[ 338.377853]
On Mon, Aug 3, 2020 at 3:01 PM Peter Humphrey wrote:
>
> On Monday, 3 August 2020 14:18:22 BST Rich Freeman wrote:
>
> > Sounds like you want --usepkgonly y --binpkg-respect-use y (the first
> > is the same as -K). At least, I think that is what you're getting at
> > - I could be
On Monday, 3 August 2020 14:18:22 BST Rich Freeman wrote:
> Sounds like you want --usepkgonly y --binpkg-respect-use y (the first
> is the same as -K). At least, I think that is what you're getting at
> - I could be misunderstanding your goal.
Not exactly. I'm finding that emerge -K installs
Can you reproduce by manually curling it?
On Sun, Aug 2, 2020, 18:41 Dale wrote:
> Howdy,
>
> I was in the middle of a update and noticed the server I was connected to
> was really slow. I edited make.conf and removed that server. I then
> restarted emerge so it would try the next server and
On Mon, Aug 3, 2020 at 7:45 AM Peter Humphrey wrote:
>
> Now, when I chroot into the rescue system and 'emerge -uaDvNk @core @base',
> portage reports that it can't use the postfix package because of different USE
> flags, but it does the update I've asked for. Postfix is in @apps in the main
>
On Mon, Aug 3, 2020 at 8:24 AM Dale wrote:
>
> In the past, I've never seen the drive on the larger files be that slow even
> toward the end. Generally, it stays pretty close to 180MBs/sec or so which
> is what I usually get with PMR drives.
Yeah, just hard to be certain without ditching the
Rich Freeman wrote:
> On Mon, Aug 3, 2020 at 1:30 AM Dale wrote:
>> Little update here. Rich, I think you mentioned it would slow down when it
>> ran out of PMR space while trying to redo the shingled part. Up until now,
>> I hadn't ran into that issue. It seems the PMR section for this
Afternoon all,
On one box here, I use the same packages and distfiles directories on both the
main system and a second, small rescue system (the latter is an alternative
boot). The rescue system has the same profile and most of the same USE flags as
its bigger brother, so the packages should
On Mon, Aug 3, 2020 at 1:30 AM Dale wrote:
>
> Little update here. Rich, I think you mentioned it would slow down when it
> ran out of PMR space while trying to redo the shingled part. Up until now, I
> hadn't ran into that issue. It seems the PMR section for this drive is
> somewhere
пн, 3 авг. 2020 г. в 11:05, Neil Bothwick :
>
> On Mon, 3 Aug 2020 02:44:43 +0300, Alexey Mishustin wrote:
>
> > This should check if 3.9 is installed:
> > if has_version '=dev-lang/python-3.9'; then
>
> Shouldn't that be has_version 'dev-lang/python:3.9' to check for any
> version of 3.9?
Sure!
On Mon, 3 Aug 2020 02:44:43 +0300, Alexey Mishustin wrote:
> > in an ebuild I have to apply a patch only if this package is installed
> > for python3.9.
> > The ebuild should work for PYTHON_COMPAT=( python3_{8,9} )
> >
> > How can I check for Pythons version in src_prepare or similar
> >
Hi,
I detected that since mid-May my main log files
/var/log/{messages,auth.log,daemon.log,...}
don't get rotated any more.
I tried to solve this by making an entry in
/etc/logrotate.conf, but that doesn't work.
"maxsize" works, but not "weekly" nor "daily".
What happened in May and what do I
15 matches
Mail list logo