On 19-02-25 14:34:46, Matthew Thode wrote:
> Allowing users to define which keyservers they update from allows them
> to work around buggy keyservers. It is also useful for local mirrors
> and / or private keyservers.
>
> It's likely that I'm setting the default incorrectly and not
>
On 19-02-25 15:41:03, Matthew Thode wrote:
> On 19-02-25 14:34:46, Matthew Thode wrote:
> > Allowing users to define which keyservers they update from allows them
> > to work around buggy keyservers. It is also useful for local mirrors
> > and / or private keyservers.
> >
> > It's likely that
On 19-02-25 15:41:03, Matthew Thode wrote:
> On 19-02-25 14:34:46, Matthew Thode wrote:
> > Allowing users to define which keyservers they update from allows them
> > to work around buggy keyservers. It is also useful for local mirrors
> > and / or private keyservers.
> >
> > It's likely that
On 19-02-25 21:59:01, Michał Górny wrote:
> On Mon, 2019-02-25 at 14:34 -0600, Matthew Thode wrote:
> > Allowing users to define which keyservers they update from allows them
> > to work around buggy keyservers. It is also useful for local mirrors
> > and / or private keyservers.
> >
> > It's
On Mon, Feb 25, 2019 at 03:09:20PM +0100, Ulrich Mueller wrote:
> > On Sun, 24 Feb 2019, Aaron Bauman wrote:
>
> > Following the feedback so far, here is v2 of the news item. [...]
>
> Sorry, looks like I replied to v1 when v2 was already out.
>
> The following still applies, though:
>
>
On Mon, 2019-02-25 at 14:34 -0600, Matthew Thode wrote:
> Allowing users to define which keyservers they update from allows them
> to work around buggy keyservers. It is also useful for local mirrors
> and / or private keyservers.
>
> It's likely that I'm setting the default incorrectly and not
Allowing users to define which keyservers they update from allows them
to work around buggy keyservers. It is also useful for local mirrors
and / or private keyservers.
It's likely that I'm setting the default incorrectly and not
alphabetizing right, but the code works at least...
--
Matthew
On 19-02-23 08:17:18, Michał Górny wrote:
> On Fri, 2019-02-22 at 20:58 -0600, Matthew Thode wrote:
> > On 19-02-19 22:05:02, Brian Dolbec wrote:
> > > On Tue, 19 Feb 2019 23:03:51 -0600
> > > Matthew Thode wrote:
> > >
> > > > On 19-02-20 00:00:04, Michael Orlitzky wrote:
> > > > > On 2/19/19
> On Sun, 24 Feb 2019, Aaron Bauman wrote:
> Following the feedback so far, here is v2 of the news item. [...]
Sorry, looks like I replied to v1 when v2 was already out.
The following still applies, though:
> Migration from both 13.0 and 17.0 profiles are supported. In case
s/are/is/
В Пн, 25/02/2019 в 13:07 +0300, Alexander Tsoy пишет:
> В Чт, 21/02/2019 в 04:36 -0500, Joshua Kinard пишет:
> > Does anyone have an idea why util-linux's build time would go up
> > significantly from 2.32.x to 2.33.x? It may be a MIPS thing, as my
> > x86_64
> > box shows no discernible change
В Чт, 21/02/2019 в 04:36 -0500, Joshua Kinard пишет:
> Does anyone have an idea why util-linux's build time would go up
> significantly from 2.32.x to 2.33.x? It may be a MIPS thing, as my
> x86_64
> box shows no discernible change in build times between the same
> versions.
> Can any other archs
Hi!
On Thu, 21 Feb 2019, Georgy Yakovlev wrote:
> On Thursday, February 21, 2019 1:36:24 AM PST Joshua Kinard wrote:
> > Does anyone have an idea why util-linux's build time would go up
> > significantly from 2.32.x to 2.33.x? It may be a MIPS thing, as my x86_64
> > box shows no discernible
12 matches
Mail list logo
