Dale wrote:
> Jack wrote:
>> On 2/28/21 4:53 PM, Dale wrote:
>>> Howdy,
>>>
>>> For the past couple weeks, this package has failed to update because it
>>> is the wrong size. This is from the logs for today.
>>>
>>>
>>> 2021-02-22 07:20:45 (96.2 KB/s) -
>>>
Jack wrote:
> On 2/28/21 4:53 PM, Dale wrote:
>> Howdy,
>>
>> For the past couple weeks, this package has failed to update because it
>> is the wrong size. This is from the logs for today.
>>
>>
>> 2021-02-22 07:20:45 (96.2 KB/s) -
>>
On 2/28/21 4:53 PM, Dale wrote:
Howdy,
For the past couple weeks, this package has failed to update because it
is the wrong size. This is from the logs for today.
2021-02-22 07:20:45 (96.2 KB/s) -
‘/var/cache/portage/distfiles/asciidoc-9.0.5.tar.gz.__download__’ saved
[1119288]
!!! Fetched
Howdy,
For the past couple weeks, this package has failed to update because it
is the wrong size. This is from the logs for today.
2021-02-22 07:20:45 (96.2 KB/s) -
‘/var/cache/portage/distfiles/asciidoc-9.0.5.tar.gz.__download__’ saved
[1119288]
!!! Fetched file: asciidoc-9.0.5.tar.gz VERIFY
On 2021-02-28 14:35-0700 Grant Taylor
wrote:
> Hi,
>
> Is the "Messages for package ..." output from emerge logged somewhere?
>
> I'd like to re-read the "Messages for package ..." output from emerge
> after the fact. Is there a concise collection of that somewhere? Or
> do I have to pilfer
On Sun, 28 Feb 2021 16:35:58 -0500,
Grant Taylor wrote:
>
> Hi,
>
> Is the "Messages for package ..." output from emerge logged somewhere?
>
> I'd like to re-read the "Messages for package ..." output from
> emerge after the fact. Is there a concise collection of that
> somewhere? Or do I
Hi,
Is the "Messages for package ..." output from emerge logged somewhere?
I'd like to re-read the "Messages for package ..." output from emerge
after the fact. Is there a concise collection of that somewhere? Or do
I have to pilfer through logs of each and every package to find it?
I'm
7 matches
Mail list logo