On April 8, 2016 4:15:04 AM GMT+02:00, Valmor de Almeida
wrote:
>On Thu, Apr 7, 2016 at 9:14 PM, R0b0t1 wrote:
>
>> Use webrsync or webrsync-gpg and see if the problem persists.
>>
>
>Waited for a few hours and tried both
>
> emerge --sync
>
>and
>
> emerge-webrsync
>
>still problematic.
>
>Tha
On Thu, Apr 7, 2016 at 9:14 PM, R0b0t1 wrote:
> Use webrsync or webrsync-gpg and see if the problem persists.
>
Waited for a few hours and tried both
emerge --sync
and
emerge-webrsync
still problematic.
Thanks for the replies.
--
Valmor
Use webrsync or webrsync-gpg and see if the problem persists.
On Fri, 8 Apr 2016 09:26:07 +1000
Sam Jorna wrote:
> On Thu, Apr 07, 2016 at 06:52:20PM -0400, Valmor de Almeida wrote:
> >Hello,
> >I have done several
> >emerge --sync
> >today but the digest verification problem below does not go away.
> >Any thoughts?
> >Thank you.
>
On Thu, Apr 07, 2016 at 06:52:20PM -0400, Valmor de Almeida wrote:
>Hello,
>I have done several
>emerge --sync
>today but the digest verification problem below does not go away.
>Any thoughts?
>Thank you.
This has been reported in Bug 579204 [0] and, as far as I am aware, w
Hello,
I have done several
emerge --sync
today but the digest verification problem below does not go away.
Any thoughts?
Thank you.
--
Valmor
>>> Fetching (165 of 221) media-libs/mesa-11.0.6::gentoo
!!! Digest verification failed:
!!! /usr/portage/media-libs/mesa/mesa-.ebuild
!!! Reason:
pe...@prh.myzen.co.uk wrote on 2016-04-07 17:24:
> I have a new box with an NVMe SSD drive attached to the PCI bus via an M.2
> interface. The drive shows up as /dev/nvme0n1, with partitions
> /dev/nvme0n1p1, /dev/nvme0n1p2, ...
>
> After following the instructions in the handbook for a UEFI sy
On Thu, Apr 7, 2016 at 5:24 PM, wrote:
> Hello list,
>
> I have a new box with an NVMe SSD drive attached to the PCI bus via an M.2
> interface. The drive shows up as /dev/nvme0n1, with partitions
> /dev/nvme0n1p1, /dev/nvme0n1p2, ...
>
> After following the instructions in the handbook for a U
Hello list,
I have a new box with an NVMe SSD drive attached to the PCI bus via an M.2
interface. The drive shows up as /dev/nvme0n1, with partitions /dev/nvme0n1p1,
/dev/nvme0n1p2, ...
After following the instructions in the handbook for a UEFI system, I get as
far as a kernel panic. Grub fi
9 matches
Mail list logo