On 2018-03-22 08:41, Ken Brown wrote:
> On 3/21/2018 8:35 PM, Brian Inglis wrote:
>> On 2018-03-21 12:14, Ken Brown wrote:
>>> On 3/20/2018 4:11 PM, Achim Gratz wrote:
Ken Brown writes:
> I'll look into both of these issues, unless Jon beats me to it.
Thanks.
> By the
On 21/03/2018 18:14, Ken Brown wrote:
On 3/20/2018 4:11 PM, Achim Gratz wrote:
Ken Brown writes:
I'll look into both of these issues, unless Jon beats me to it.
Thanks.
By the way, this only affects local installs. For network installs,
the hash gets checked at an earlier stage.
That's
On 3/21/2018 8:35 PM, Brian Inglis wrote:
On 2018-03-21 12:14, Ken Brown wrote:
On 3/20/2018 4:11 PM, Achim Gratz wrote:
Ken Brown writes:
I'll look into both of these issues, unless Jon beats me to it.
Thanks.
By the way, this only affects local installs. For network installs,
the hash
On 2018-03-21 12:14, Ken Brown wrote:
> On 3/20/2018 4:11 PM, Achim Gratz wrote:
>> Ken Brown writes:
>>> I'll look into both of these issues, unless Jon beats me to it.
>>
>> Thanks.
>>
>>> By the way, this only affects local installs. For network installs,
>>> the hash gets checked at an
On 3/20/2018 4:11 PM, Achim Gratz wrote:
Ken Brown writes:
I'll look into both of these issues, unless Jon beats me to it.
Thanks.
By the way, this only affects local installs. For network installs,
the hash gets checked at an earlier stage.
That's correct. I forgot to mention that, but
Ken Brown writes:
> I'll look into both of these issues, unless Jon beats me to it.
Thanks.
> By the way, this only affects local installs. For network installs,
> the hash gets checked at an earlier stage.
That's correct. I forgot to mention that, but all my installs are from
a local mirror
On 3/20/2018 2:23 PM, Achim Gratz wrote:
I've found out the hard way that a dodgy package file no longer gets
ignored by setup and is installed without any error unless you care to
look in setup.log.full. That was hard to figure out because in my case
some stupid error on mirroring just made
I've found out the hard way that a dodgy package file no longer gets
ignored by setup and is installed without any error unless you care to
look in setup.log.full. That was hard to figure out because in my case
some stupid error on mirroring just made each file miss a few bytes off
the end, so