dear Franco
On Sun, 26 Apr 2015, Franco Lanza wrote:
> The issue was caused by a down debian mirror repository from where
> amprolla was requesting files to update the merged repo that was
> causing amprolla to fail.
>
> It's now fixed, and in a matter of 20 mins from now ( 01:24am italy
> time)
On Sat, Apr 25, 2015 at 04:50:34PM +0200, Irrwahn wrote:
>
> You're welcome. :)
>
> I think we just have to wait for the Devuan tech staff to
> update the release files in their repositories. So, from our
> user perspective, the problem will simply go away eventually.
> The same actually happe
You're welcome. :)
I think we just have to wait for the Devuan tech staff to
update the release files in their repositories. So, from our
user perspective, the problem will simply go away eventually.
The same actually happened a few weeks ago (hence I knew about
the workaround) and it was reso
(problem==error)
On 25/04/15 16:20, Paweł Cholewiński wrote:
Thanks Urban, it works.
But how to remove source of the problem? I read that is repository
problem.
Paweł
On 25/04/15 15:19, Irrwahn wrote:
Hi,
a temporary workaround would be:
apt-get -o Acquire::Check-Valid-Until=false upda
Thanks Urban, it works.
But how to remove source of the problem? I read that is repository problem.
Paweł
On 25/04/15 15:19, Irrwahn wrote:
Hi,
a temporary workaround would be:
apt-get -o Acquire::Check-Valid-Until=false update
Or, in case you prefer aptitude:
aptitude -o Acquire::Chec
Hi,
a temporary workaround would be:
apt-get -o Acquire::Check-Valid-Until=false update
Or, in case you prefer aptitude:
aptitude -o Acquire::Check-Valid-Until=false update
[And hello to the list from me, too! :) Been lurking here for
a while. Please keep up the good work at Devuan, look
