Ask your questions here.
Post a reply

[SOLVED] "Release file for...is expired" in the apt update

Sat Nov 05, 2016 9:47 am

Hi, For the first time to post to this forum.

I have obtained the following output than the previous few hours "apt update":

Code:
[email protected]:~$ LANG=C sudo apt-get update
Hit http://auto.mirror.devuan.org jessie InRelease
Ign http://download.opensuse.org  InRelease                           
Hit http://download.opensuse.org  Release.gpg                         
Hit http://auto.mirror.devuan.org jessie-updates InRelease                   
Hit http://download.opensuse.org  Release                                     
Hit http://auto.mirror.devuan.org jessie-security InRelease         
Get:1 http://auto.mirror.devuan.org jessie/main i386 Packages [6797 kB]
E: Release file for http://auto.mirror.devuan.org/merged/dists/jessie-security/InRelease is expired (invalid since 11h 28min 48s). Updates for this repository will not be applied.
[email protected]:~$

I forum and documentation of this Refracta, also Devuan side was also confirmed,
but the information was not there as well.
Please reply if there is an improvement method.
Last edited by balloon on Fri Nov 11, 2016 10:44 am, edited 1 time in total.

Re: "Release file for...is expired" in the apt update

Sat Nov 05, 2016 12:06 pm

This is new. There is obviously a problem with the repository. Aptitude tells me there are 1169 updates available. That can't be right - this system was upgraded last week. DO NOT UPGRADE AT THIS TIME.

With any luck, this will get fixed today. Maybe I'll try update/upgrade on one of my test systems that I don't mind screwing up.

Re: "Release file for...is expired" in the apt update

Sat Nov 05, 2016 3:04 pm

understood. I will wait for fix.

Re: "Release file for...is expired" in the apt update

Sat Nov 05, 2016 3:38 pm

I read this on the devuan mailing list this morning,
For anyone looking for a tempory workaround, try:

sudo apt-get -o Acquire::Check-Valid-Until=false update

It seems to work, but my install(s) were already up to date, so it shows no new updates available. However, all the update files seem to download.

EDIT: You may want to hold off on this update for a while. I just tried this with an older install and I get some error 404 messages from the debian-security repo, which ties into the devuan repo.

Re: "Release file for...is expired" in the apt update

Sat Nov 05, 2016 4:00 pm

I ran that line, and it reduced the available updates from 1169 to 6. More believable. But I didn't try the actual upgrade. I'm hoping it will get fixed today.

Re: "Release file for...is expired" in the apt update

Sat Nov 05, 2016 4:49 pm

I just did an update, got the failure message but have no upgrades waiting.

Re: "Release file for...is expired" in the apt update

Sun Nov 06, 2016 7:39 pm

The problem has been corrected. You can do a normal update/upgrade now.

Re: "Release file for...is expired" in the apt update

Mon Nov 07, 2016 2:33 am

I run the apt update, it has confirmed its normal operation.

Re: "Release file for...is expired" in the apt update

Tue Nov 08, 2016 10:26 am

Here is an explanation of what happened.

https://lists.dyne.org/lurker/message/2 ... e8.en.html
Author: hellekin
Date: 2016-11-08 09:20 UTC
To: dng
Subject: [DNG] Recent Security Update Discrepancy
As you may have noticed, last week-end the security updates for JESSIE
and ASCII didn't work. We apologize for that glitch which reminds us
we're still in Beta. The problem was fixed and shouldn't happen again.

Recent changes in the devuan-keyring package made that the secondary
instance of Amprolla that's running the jessie-security and
ascii-security sessions was failing to check the cryptographic signature
on the InRelease file, and therefore was not updating packages.

The devuan-keyring was updated to comply to the latest format in Debian
and its derivatives that split the maintainers and archives/repositories
keyrings.

The secondary Amprolla session configuration was overlooked and kept
looking for the key in the old /usr/share/keyrings/devuan.gpg instead of
the new /usr/share/keyrings/devuan-archive-keyring.gpg.

The configuration file of Amprolla is supposed to seldom change if at
all, and the mind map of the sysadmins is now updated on this possibility.

The failure happened on a week-end, which made its resolution much
slower than usual (about 2 days), especially as everyone is rushing to
prepare a new beta version of JESSIE that will act as an Release Candidate.

Thank you for your patience,

==
hk
Post a reply