On Wed, Jul 4, 2018 at 5:43 PM gevisz wrote:
>
> but it "shot" only after sourcing /etc/profile.
Which is what "su -l" does.
On Wed, Jul 4, 2018 at 5:39 PM gevisz wrote:
> 2018-07-03 16:22 GMT+03:00 Mart Raudsepp :
>> If you use su, you should be using "su -" (or "su -l" or "su --login"),
>> not "su".
>
> I have used only "su" for already 3 years, since switched to Gentoo
> from Ubuntu and never had any problems with
On Wed, Jul 4, 2018 at 1:34 PM Rich Freeman wrote:
>
> I wonder if we can have portage instead do a fetch, then do the
> verification of HEAD, and then if it passes do a checkout. That will
> still leave you with invalid data in the git history, but it won't
> actually be checked out, so at
2018-07-04 21:00 GMT+03:00 Jack :
> On 2018.07.04 13:38, gevisz wrote:
>>
>> 2018-07-03 16:22 GMT+03:00 Mart Raudsepp :
>> > Ühel kenal päeval, T, 03.07.2018 kell 14:00, kirjutas gevisz:
Are you, by any chance, running this command through something like
lxc-attach or ssh?
>
On 2018.07.04 13:38, gevisz wrote:
2018-07-03 16:22 GMT+03:00 Mart Raudsepp :
> Ühel kenal päeval, T, 03.07.2018 kell 14:00, kirjutas gevisz:
Are you, by any chance, running this command through something like
lxc-attach or ssh?
I had the exact same problem two days ago and it turned out to be
2018-07-03 23:55 GMT+03:00 R0b0t1 :
>
> It looks like you resolved the issue.
Yes.
> I had to refresh the keys multiple times.
I also refreshed them many times but it "shot" only after sourcing /etc/profile.
2018-07-03 16:22 GMT+03:00 Mart Raudsepp :
> Ühel kenal päeval, T, 03.07.2018 kell 14:00, kirjutas gevisz:
>> Are you, by any chance, running this command through something like
>> > lxc-attach or ssh?
>> > I had the exact same problem two days ago and it turned out to be
>> > something about the
On Wed, Jul 4, 2018 at 12:20 PM gevisz wrote:
>
> 2018-07-03 16:04 GMT+03:00 Rich Freeman :
>
> > emerge --sync, with git at least, overwrites /usr/portage in place and
> > so it will leave it in a bad state if verification fails.
>
> It sounds really aweful.
> I did not know this as I always
2018-07-03 16:04 GMT+03:00 Rich Freeman :
> On Tue, Jul 3, 2018 at 8:44 AM gevisz wrote:
>>
>> 2018-07-03 14:47 GMT+03:00 Rich Freeman :
>> > On Tue, Jul 3, 2018 at 7:06 AM gevisz wrote:
>> >>
>> >> Why not to put new openpgp-keys-gentoo-release
>> >> into the portage tree BEFORE all existing
On Tue, Jul 3, 2018 at 6:00 AM, gevisz wrote:
> 2018-07-03 13:35 GMT+03:00 Virgil Dupras :
>> On Tue, 03 Jul 2018 09:55:38 +0100
>> Mick wrote:
>>
>>> On Tuesday, 3 July 2018 09:53:27 BST Arve Barsnes wrote:
>>> > On 3 July 2018 at 09:48, gevisz wrote:
>>> > > Trying to renew them manually with
On 3 July 2018 at 15:22, Mart Raudsepp wrote:
> How do you obtain root privileges for the command?
>
> If you use su, you should be using "su -" (or "su -l" or "su --login"),
> not "su".
I did not need to do so to make this work.
It all depends on the environment you start out with I guess.
Ühel kenal päeval, T, 03.07.2018 kell 14:00, kirjutas gevisz:
> Are you, by any chance, running this command through something like
> > lxc-attach or ssh?
> > I had the exact same problem two days ago and it turned out to be
> > something about the
> > environment being passed to the remote
On Tue, Jul 3, 2018 at 8:44 AM gevisz wrote:
>
> 2018-07-03 14:47 GMT+03:00 Rich Freeman :
> > On Tue, Jul 3, 2018 at 7:06 AM gevisz wrote:
> >>
> >> Why not to put new openpgp-keys-gentoo-release
> >> into the portage tree BEFORE all existing Gentoo
> >> singing keys expire?
> >>
> >
> > My
2018-07-03 14:47 GMT+03:00 Rich Freeman :
> On Tue, Jul 3, 2018 at 7:06 AM gevisz wrote:
>>
>> Why not to put new openpgp-keys-gentoo-release
>> into the portage tree BEFORE all existing Gentoo
>> singing keys expire?
>>
>
> My guess is that it was an oversight.
>
> I note that emerge --sync
On Tue, Jul 3, 2018 at 7:06 AM gevisz wrote:
>
> Why not to put new openpgp-keys-gentoo-release
> into the portage tree BEFORE all existing Gentoo
> singing keys expire?
>
My guess is that it was an oversight.
I note that emerge --sync seems to update keys from the keyserver
automatically, and
2018-07-03 13:41 GMT+03:00 gevisz :
> 2018-07-03 11:10 GMT+03:00 Mick :
>> On Tuesday, 3 July 2018 08:48:02 BST gevisz wrote:
...
>>
>> This package update came up yesterday:
>>
>> app-crypt/openpgp-keys-gentoo-release-20180702
>>
>
> Too late: Gentoo signing keys expired on 1 July 2018.
> So, no
2018-07-03 13:35 GMT+03:00 Virgil Dupras :
> On Tue, 03 Jul 2018 09:55:38 +0100
> Mick wrote:
>
>> On Tuesday, 3 July 2018 09:53:27 BST Arve Barsnes wrote:
>> > On 3 July 2018 at 09:48, gevisz wrote:
>> > > Trying to renew them manually with the following commands does not help:
>> > >
>> > > #
2018-07-03 11:53 GMT+03:00 Arve Barsnes :
> On 3 July 2018 at 09:48, gevisz wrote:
>> Trying to renew them manually with the following commands does not help:
>>
>> # gpg --keyserver hkps.pool.sks-keyservers.net --recv-keys 0x825533CBF6CD6C97
>
> It solved itself for me after running
> gpg
2018-07-03 11:10 GMT+03:00 Mick :
> On Tuesday, 3 July 2018 08:48:02 BST gevisz wrote:
>> Just today I have tried emerge-webrsync and got
>> to the following endless circle:
>>
>> Fetching most recent snapshot ...
>> Trying to retrieve 20180702 snapshot from http://mirror.netcologne.de/gentoo
>>
On Tue, 03 Jul 2018 09:55:38 +0100
Mick wrote:
> On Tuesday, 3 July 2018 09:53:27 BST Arve Barsnes wrote:
> > On 3 July 2018 at 09:48, gevisz wrote:
> > > Trying to renew them manually with the following commands does not help:
> > >
> > > # gpg --keyserver hkps.pool.sks-keyservers.net
On 3 July 2018 at 10:55, Mick wrote:
> # gpg --homedir /var/lib/gentoo/gkeys/keyrings/gentoo/release --refresh-keys
> gpg: keyblock resource '/var/lib/gentoo/gkeys/keyrings/gentoo/release/
> pubring.kbx': No such file or directory
>
> :-/
Hmm...
I don't have this file either, but had no
On Tuesday, 3 July 2018 09:53:27 BST Arve Barsnes wrote:
> On 3 July 2018 at 09:48, gevisz wrote:
> > Trying to renew them manually with the following commands does not help:
> >
> > # gpg --keyserver hkps.pool.sks-keyservers.net --recv-keys
> > 0x825533CBF6CD6C97
> It solved itself for me after
On 3 July 2018 at 09:48, gevisz wrote:
> Trying to renew them manually with the following commands does not help:
>
> # gpg --keyserver hkps.pool.sks-keyservers.net --recv-keys 0x825533CBF6CD6C97
It solved itself for me after running
gpg --homedir /var/lib/gentoo/gkeys/keyrings/gentoo/release
On Tuesday, 3 July 2018 08:48:02 BST gevisz wrote:
> Just today I have tried emerge-webrsync and got
> to the following endless circle:
>
> Fetching most recent snapshot ...
> Trying to retrieve 20180702 snapshot from http://mirror.netcologne.de/gentoo
> ... Fetching file
Just today I have tried emerge-webrsync and got
to the following endless circle:
Fetching most recent snapshot ...
Trying to retrieve 20180702 snapshot from http://mirror.netcologne.de/gentoo ...
Fetching file portage-20180702.tar.xz.md5sum ...
Fetching file portage-20180702.tar.xz.gpgsig ...
25 matches
Mail list logo
