ср, 9 янв. 2019 г. в 22:17, Rich Freeman :
>
> On Wed, Jan 9, 2019 at 2:38 PM gevisz wrote:
> >
> > ср, 9 янв. 2019 г. в 19:36, Rich Freeman :
> > >
> > > On Wed, Jan 9, 2019 at 6:21 AM gevisz wrote:
> > > >
> > > > On the other side, app-crypt/gkeys is marked by ~
> > > > in my architecture
On Wed, Jan 9, 2019 at 2:38 PM gevisz wrote:
>
> ср, 9 янв. 2019 г. в 19:36, Rich Freeman :
> >
> > On Wed, Jan 9, 2019 at 6:21 AM gevisz wrote:
> > >
> > > On the other side, app-crypt/gkeys is marked by ~
> > > in my architecture (amd64). So, it is impossible
> > > to update the portage
ср, 9 янв. 2019 г. в 19:36, Rich Freeman :
>
> On Wed, Jan 9, 2019 at 6:21 AM gevisz wrote:
> >
> > Just tonight I tried to update my portage snapshot
> > by emerge-webrsync command and found out that
> > the portage snapshot signing key expired again
> > without being properly updated by
On Wed, Jan 9, 2019 at 6:21 AM gevisz wrote:
>
> Just tonight I tried to update my portage snapshot
> by emerge-webrsync command and found out that
> the portage snapshot signing key expired again
> without being properly updated by app-crypt/gentoo-keys
> update before its expiration as
Just tonight I tried to update my portage snapshot
by emerge-webrsync command and found out that
the portage snapshot signing key expired again
without being properly updated by app-crypt/gentoo-keys
update before its expiration as described here:
5 matches
Mail list logo