Brian wrote:
On Fri 09 Nov 2018 at 08:32:57 -0500, Boyan Penkov wrote:
On apt-get update, I see:
Reading package lists... Done
E: Release file for
http://mirror.cc.columbia.edu/debian/dists/buster/InRelease is expired
(invalid since 17h 5min 48s). Updates for this repository will not be
On 11/9/18, Brian wrote:
> On Fri 09 Nov 2018 at 08:32:57 -0500, Boyan Penkov wrote:
>
>> On apt-get update, I see:
>>
>> Reading package lists... Done
>> E: Release file for
>> http://mirror.cc.columbia.edu/debian/dists/buster/InRelease is expired
>> (invalid since 17h 5min 48s). Updates for
On 11/9/18, Boyan Penkov wrote:
> On apt-get update, I see:
>
> Reading package lists... Done
> E: Release file for
> http://mirror.cc.columbia.edu/debian/dists/buster/InRelease is expired
> (invalid since 17h 5min 48s). Updates for this repository will not be
> applied.
>
> What's the best way
On Fri 09 Nov 2018 at 08:32:57 -0500, Boyan Penkov wrote:
> On apt-get update, I see:
>
> Reading package lists... Done
> E: Release file for
> http://mirror.cc.columbia.edu/debian/dists/buster/InRelease is expired
> (invalid since 17h 5min 48s). Updates for this repository will not be
>
On apt-get update, I see:
Reading package lists... Done
E: Release file for
http://mirror.cc.columbia.edu/debian/dists/buster/InRelease is expired
(invalid since 17h 5min 48s). Updates for this repository will not be
applied.
What's the best way to communicate this to the folks who manage that
5 matches
Mail list logo