Michał Górny posted on Wed, 24 Jan 2018 20:58:54 +0100 as excerpted:
> W dniu śro, 24.01.2018 o godzinie 12∶54 -0500, użytkownik Alec Warner
> napisał:
>>
>> I think its a bit trickier to control the hook's behavior. For
>> instance:
>>
>> 1) I install portage[rsync-verify]. This installs the
On 01/24/2018 01:36 PM, Michał Górny wrote:
> Add two new configuration options to rsync repositories:
> sync-rsync-verify-metamanifest and sync-rsync-openpgp-key-path.
> The first controls whether gemato verification is run for
> the repository (defaults to true for ::gentoo, false otherwise),
>
Add two new configuration options to rsync repositories:
sync-rsync-verify-metamanifest and sync-rsync-openpgp-key-path.
The first controls whether gemato verification is run for
the repository (defaults to true for ::gentoo, false otherwise),
the second makes it possible to override the key path
Add two new configuration options to rsync repositories:
sync-rsync-verify-metamanifest and sync-rsync-openpgp-key-path.
The first controls whether gemato verification is run for
the repository (defaults to true for ::gentoo, false otherwise),
the second makes it possible to override the key path
Add two new configuration options to rsync repositories:
sync-rsync-verify-metamanifest and sync-rsync-openpgp-key-path.
The first controls whether gemato verification is run for
the repository (defaults to true for ::gentoo, false otherwise),
the second makes it possible to override the key path
On 01/24/2018 01:03 PM, Michał Górny wrote:
> diff --git a/pym/portage/sync/modules/rsync/rsync.py
> b/pym/portage/sync/modules/rsync/rsync.py
> index c80641ba3..f3157d093 100644
> --- a/pym/portage/sync/modules/rsync/rsync.py
> +++ b/pym/portage/sync/modules/rsync/rsync.py
> @@ -1,4 +1,4 @@
> -#
Add two new configuration options to rsync repositories:
sync-rsync-verify-metamanifest and sync-rsync-openpgp-key-path.
The first controls whether gemato verification is run for
the repository (defaults to true for ::gentoo, false otherwise),
the second makes it possible to override the key path
W dniu śro, 24.01.2018 o godzinie 12∶29 -0800, użytkownik Zac Medico
napisał:
> On 01/24/2018 12:56 AM, Michał Górny wrote:
> > Hi, everyone.
> >
> > Since the initial review of my patch lost focus, and lacked sufficient
> > context, here's the plan that I'd like to follow in order to initially
On 01/24/2018 12:56 AM, Michał Górny wrote:
> Hi, everyone.
>
> Since the initial review of my patch lost focus, and lacked sufficient
> context, here's the plan that I'd like to follow in order to initially
> integrate gemato with portage and give our users secure checkouts by default.
>
> 1.
On Wed, Jan 24, 2018 at 2:58 PM, Michał Górny wrote:
> W dniu śro, 24.01.2018 o godzinie 12∶54 -0500, użytkownik Alec Warner
> napisał:
> > On Wed, Jan 24, 2018 at 3:56 AM, Michał Górny wrote:
> >
> > > Hi, everyone.
> > >
> > > Since the initial review of
W dniu śro, 24.01.2018 o godzinie 12∶54 -0500, użytkownik Alec Warner
napisał:
> On Wed, Jan 24, 2018 at 3:56 AM, Michał Górny wrote:
>
> > Hi, everyone.
> >
> > Since the initial review of my patch lost focus, and lacked sufficient
> > context, here's the plan that I'd like
On Wed, Jan 24, 2018 at 3:56 AM, Michał Górny wrote:
> Hi, everyone.
>
> Since the initial review of my patch lost focus, and lacked sufficient
> context, here's the plan that I'd like to follow in order to initially
> integrate gemato with portage and give our users secure
Hi, everyone.
Since the initial review of my patch lost focus, and lacked sufficient context,
here's the plan that I'd like to follow in order to initially integrate gemato
with portage and give our users secure checkouts by default.
1. Add postsync hook to Portage git. Eventually, it will be
13 matches
Mail list logo