On Sun, Dec 16, 2018 at 02:30:31PM +0100, Vagrant Cascadian wrote:
> On 2018-12-16, Vagrant Cascadian wrote:
> > On 2018-12-16, Wolfgang Schweer wrote:
> >> On Sun, Dec 16, 2018 at 09:30:21AM +0100, Vagrant Cascadian wrote:
> >>> On 2018-12-16, Vagrant Cascadian wrote:
> >>> > I'm now thinking of
On Sun, Dec 16, 2018 at 02:30:31PM +0100, Vagrant Cascadian wrote:
> Ah, I see the problem. It was not because it was evaluated too late, but
> because you thought it was a boolean. I should make it a proper boolean,
> rather than the way it's currently configured.
>
> If using a configuration
On 2018-12-16, Vagrant Cascadian wrote:
> On 2018-12-16, Wolfgang Schweer wrote:
>> On Sun, Dec 16, 2018 at 09:30:21AM +0100, Vagrant Cascadian wrote:
>>> On 2018-12-16, Vagrant Cascadian wrote:
>>> > I'm now thinking of passing an option --trust-file-mirrors or something
>>> > like that. Then the
On 2018-12-16, Wolfgang Schweer wrote:
> On Sun, Dec 16, 2018 at 09:30:21AM +0100, Vagrant Cascadian wrote:
>> On 2018-12-16, Vagrant Cascadian wrote:
>> > I'm now thinking of passing an option --trust-file-mirrors or something
>> > like that. Then the trust is explicit, consistent with apt
On Sun, Dec 16, 2018 at 09:30:21AM +0100, Vagrant Cascadian wrote:
> On 2018-12-16, Vagrant Cascadian wrote:
> > I'm now thinking of passing an option --trust-file-mirrors or something
> > like that. Then the trust is explicit, consistent with apt behavior
> > requiring to explicitly trust it. It
On 2018-12-16, Vagrant Cascadian wrote:
> I'm now thinking of passing an option --trust-file-mirrors or something
> like that. Then the trust is explicit, consistent with apt behavior
> requiring to explicitly trust it. It wouldn't allow different levels of
> trust for different file mirror types,
On 2018-12-10, Wolfgang Schweer wrote:
> On Sat, Dec 08, 2018 at 03:08:22PM +0100, Vagrant Cascadian wrote:
>> On 2018-12-07, Vagrant Cascadian wrote:
>> But it's also possible to have some mirrors include a file:/// url
>> that's trusted and some that are not... so it needs to be specified on a
On Sat, Dec 08, 2018 at 03:08:22PM +0100, Vagrant Cascadian wrote:
> On 2018-12-07, Vagrant Cascadian wrote:
> But it's also possible to have some mirrors include a file:/// url
> that's trusted and some that are not... so it needs to be specified on a
> per-mirror basis.
Just another try w/
On 2018-12-07, Vagrant Cascadian wrote:
> On 2018-10-20, Wolfgang Schweer wrote:
>> Due to security concerns, file:/// repositories are no longer considered to
>> be
>> trusted by default. If a complete ISO image is used to install LTSP in
>> offline
>> mode, such a repository is actually
On 2018-10-20, Wolfgang Schweer wrote:
> From e643e524802668c43ced718df07c43e80d1978dd Mon Sep 17 00:00:00 2001
> From: Wolfgang Schweer
> Date: Sat, 20 Oct 2018 10:36:57 +0200
> Subject: [PATCH] Adjust server/Debian/share/ltsp/ltsp-build-client-functions
> to be apt compliant.
>
> Due to
10 matches
Mail list logo
