How to work around “Release file expired” problem on a local mirror
I have a local mirror (created with debmirror), and when I run apt-get update after a few days, I get this:
E: Release file expired, ignoring file:/home/wena/.repo_bin/dists/sid/Release (invalid since 14h 31min 45s)
How do I work around that?
apt
asked Sep 30 '10 at 10:49
TshepangTshepang
26.4k72187265
add a comment |
I have a local mirror (created with debmirror), and when I run apt-get update after a few days, I get this:
E: Release file expired, ignoring file:/home/wena/.repo_bin/dists/sid/Release (invalid since 14h 31min 45s)
How do I work around that?
apt
asked Sep 30 '10 at 10:49
TshepangTshepang
26.4k72187265
4
Security Warning: This question asks for a work around. However it is better to fix the mirror or point to a working one. I changed to point at httpredir.debian.org/debian and it started working again.
– ctrl-alt-delor
Jun 2 '17 at 7:37
Switch to a different mirror and it'll work.
– Patrick Mutwiri
Jul 21 '18 at 12:49
2
What is "better" depends on what your goals are. If your goal is to get the latest packages from Debian then changing mirror is the right soloution. If your goal is to use the older mirror that you have locally so you can get on with your work where Internet is unavailable or expensive then turning off the expiry check is the right solution. If your goal is to update to a specific older version of the repo for bug triage reasons then again turning off the expiry check is the right solution.
– plugwash
Sep 20 '18 at 19:11
add a comment |
I have a local mirror (created with debmirror), and when I run apt-get update after a few days, I get this:
E: Release file expired, ignoring file:/home/wena/.repo_bin/dists/sid/Release (invalid since 14h 31min 45s)
How do I work around that?
apt
asked Sep 30 '10 at 10:49
TshepangTshepang
26.4k72187265
I have a local mirror (created with debmirror), and when I run apt-get update after a few days, I get this:
E: Release file expired, ignoring file:/home/wena/.repo_bin/dists/sid/Release (invalid since 14h 31min 45s)
How do I work around that?
apt
apt
asked Sep 30 '10 at 10:49
TshepangTshepang
26.4k72187265
asked Sep 30 '10 at 10:49
TshepangTshepang
26.4k72187265
edited Apr 21 '15 at 13:46
Tshepang
asked Sep 30 '10 at 10:49
TshepangTshepang
26.4k72187265
asked Sep 30 '10 at 10:49
TshepangTshepang
26.4k72187265
asked Sep 30 '10 at 10:49
TshepangTshepang
26.4k72187265
26.4k72187265
4
Security Warning: This question asks for a work around. However it is better to fix the mirror or point to a working one. I changed to point at httpredir.debian.org/debian and it started working again.
– ctrl-alt-delor
Jun 2 '17 at 7:37
Switch to a different mirror and it'll work.
– Patrick Mutwiri
Jul 21 '18 at 12:49
2
What is "better" depends on what your goals are. If your goal is to get the latest packages from Debian then changing mirror is the right soloution. If your goal is to use the older mirror that you have locally so you can get on with your work where Internet is unavailable or expensive then turning off the expiry check is the right solution. If your goal is to update to a specific older version of the repo for bug triage reasons then again turning off the expiry check is the right solution.
– plugwash
Sep 20 '18 at 19:11
add a comment |
4
Security Warning: This question asks for a work around. However it is better to fix the mirror or point to a working one. I changed to point at httpredir.debian.org/debian and it started working again.
– ctrl-alt-delor
Jun 2 '17 at 7:37
Switch to a different mirror and it'll work.
– Patrick Mutwiri
Jul 21 '18 at 12:49
2
What is "better" depends on what your goals are. If your goal is to get the latest packages from Debian then changing mirror is the right soloution. If your goal is to use the older mirror that you have locally so you can get on with your work where Internet is unavailable or expensive then turning off the expiry check is the right solution. If your goal is to update to a specific older version of the repo for bug triage reasons then again turning off the expiry check is the right solution.
– plugwash
Sep 20 '18 at 19:11
4
4
Security Warning: This question asks for a work around. However it is better to fix the mirror or point to a working one. I changed to point at httpredir.debian.org/debian and it started working again.
– ctrl-alt-delor
Jun 2 '17 at 7:37
Security Warning: This question asks for a work around. However it is better to fix the mirror or point to a working one. I changed to point at httpredir.debian.org/debian and it started working again.
– ctrl-alt-delor
Jun 2 '17 at 7:37
Switch to a different mirror and it'll work.
– Patrick Mutwiri
Jul 21 '18 at 12:49
Switch to a different mirror and it'll work.
– Patrick Mutwiri
Jul 21 '18 at 12:49
2
2
What is "better" depends on what your goals are. If your goal is to get the latest packages from Debian then changing mirror is the right soloution. If your goal is to use the older mirror that you have locally so you can get on with your work where Internet is unavailable or expensive then turning off the expiry check is the right solution. If your goal is to update to a specific older version of the repo for bug triage reasons then again turning off the expiry check is the right solution.
– plugwash
Sep 20 '18 at 19:11
What is "better" depends on what your goals are. If your goal is to get the latest packages from Debian then changing mirror is the right soloution. If your goal is to use the older mirror that you have locally so you can get on with your work where Internet is unavailable or expensive then turning off the expiry check is the right solution. If your goal is to update to a specific older version of the repo for bug triage reasons then again turning off the expiry check is the right solution.
– plugwash
Sep 20 '18 at 19:11
add a comment |
8 Answers
8
active
oldest
votes
Add this to the command:
-o Acquire::Check-Valid-Until=false
For example:
sudo apt-get -o Acquire::Check-Valid-Until=false update
edited Feb 8 '16 at 8:46
Tshepang
26.4k72187265
answered Aug 21 '12 at 8:23
A AA A
74662
10
This worked, but some explanation of why it did would be useful.
– Faheem Mitha
Sep 9 '14 at 23:17
2
This deactivates the check which verifies expired digital signatures, so apt will accept old and expired release keys as well.
– grin
May 31 '17 at 11:05
5
Security Warning: This answer is a work around (as asked for). However it is better to fix the mirror or point to a working one. I changed to point at httpredir.debian.org/debian and it started working again.
– ctrl-alt-delor
Jun 2 '17 at 7:36
2
you cannot switch that easily for already deprecated releases like say debian 6 where you need to use archives.debian.org to get any packages now
– Marcin Orlowski
Aug 23 '18 at 13:46
add a comment |
If you do not care about this check, no matter for which mirror, just create a file in /etc/apt/apt.conf.d/ (e.g. name it 10no--check-valid-until) and put the option directly in there:
Acquire::Check-Valid-Until "0";
After this, you will never be bothered again with the mentioned warning at all.
answered Feb 24 '15 at 7:24
JaleksJaleks
1,496624
1
Although the workaround itself isn't the optimal solution, I have a development box that I don't care about, so this annoyance simply gets in my way. I was able to use this answer with Ansible since I can't find any way to add the accepted answer to the action module when using ansible_pkg_mgr.
– jia103
Nov 11 '16 at 23:44
add a comment |
The release files have a valid-until entry, e.g. Valid-Until: Thu, 07 Oct 2010 08:17:56 UTC
If the release file isn't valid anymore, you should run debmirror again to check if there are any changes in the repository. One change will be the release file and you will get a new validity for it.
You could easily automate this with a crontab entry.
answered Sep 30 '10 at 11:42
echoxechox
13.1k43953
Thanks for that one. I should have looked inside that file before asking. Curiously though, is this a new thing? It didn't happen before (but once).
– Tshepang
Sep 30 '10 at 11:58
I don't use debian really often at the moment, but maybe they just changed the release file cycles to a shorter date...
– echox
Sep 30 '10 at 12:03
add a comment |
Some of the mirrors out there might have stale files. This happened to me recently, and it was in also tied to the caching server I'm using (apt-cacher-ng) which tries to save bandwidth by redirecting the repositories for same archive to a single entity (in my case if was a Hungarian mirror). Direct updates through German mirror worked ok, for example. Try changing the mirror you're using. In case you're using apt-cacher-ng, you'll need to do something in the line of changing the following file's contents:
- /etc/apt-cacher-ng/backends_debian
- /etc/apt-cacher-ng/backends_debvol
After that you should also restart apt-cacher-ng for changes to take effect.
edited Aug 10 '15 at 13:35
Tshepang
26.4k72187265
Note that I was asking for a workaround, not why this was happening (good answer though). In this case I was, knowingly, having a stale repository.
– Tshepang
May 13 '11 at 12:44
add a comment |
This can also happen if your system date/time is wrong. I fixed it by correcting my local time before doing the update.
edited Sep 19 '18 at 20:51
Michael Mrozek♦
62.2k29193213
answered Sep 19 '18 at 20:08
MarrekNožkaMarrekNožka
311
@AnthonyGeoghegan It does for me. This is the only thing that worked in the end.
– Martin Vseticka
Jan 30 at 22:28
1
@MartinVseticka You’re right. I made that comment when I came across this answer in one of the review queues after the system flagged it for moderation. The original wording (before Michael edited it) was far less useful.
– Anthony Geoghegan
Jan 31 at 10:13
add a comment |
I removed /var/lib/apt/* and rerun apt-get update, and it works!
edited Jan 12 '15 at 20:40
HalosGhost
3,78392236
answered Jan 12 '15 at 20:24
PatrickPatrick
1643
I do that for a completely different error, and it works for that one. This error is completely irrelevant.
– snetch
Jul 10 '17 at 17:21
add a comment |
The mirror might not be expired.
Rather something else on your system might be messed up. Try this:
1) Temporarily comment out related lines from from /etc/apt/sources.list, or /etc/apt/source.list.d/*. For example after I commented out the following two lines, my error went away, (with the consequence that these archives were temporarily not used for reloads):
deb http://security.debian.org/ stretch/updates non-free contrib main
deb http://mirrors.ocf.berkeley.edu/debian/ stretch-updates main contrib non-free
2) Open synaptic and reload, or probably sudo apt-get update would also work.
3) Comment these lines back in.
4) Repeat step 2.
Fixed this for me. I'm guessing my apt cache got a bad date in it.
My problem occurred after restoring my / (root) and /var filesystems from btrfs snapshots to help fix a package install problem that occurred. The exact error message that I was getting was:
Release file for
http://mirrors.ocf.berkeley.edu/debian/dists/stretch-updates/InRelease
is expired (invalid since 5d 4h 50min 18s). Updates for this
repository will not be applied. Release file for
http://security.debian.org/dists/stretch/updates/InRelease is expired
(invalid since 2d 2h 52min 43s). Updates for this repository will not
be applied.
answered Feb 19 '18 at 0:12
Elliptical viewElliptical view
6231623
add a comment |
Not sure whether its related with Jessie current issue (https://lists.debian.org/debian-devel-announce/2019/03/msg00006.html) or not. but for those got a same error even already used "sudo apt-get -o Acquire::Check-Valid-Until=false update" and still occurred a same issue, can try this instead "echo 'Acquire::Check-Valid-Until no;' > /etc/apt/apt.conf.d/99no-check-valid-until"
It works for me :)
Thanks!
answered 13 mins ago
Alex ChandraAlex Chandra
11
New contributor
Alex Chandra is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f2544%2fhow-to-work-around-release-file-expired-problem-on-a-local-mirror%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
8 Answers
8
active
oldest
votes
8 Answers
8
active
oldest
votes
active
oldest
votes
active
oldest
votes
Add this to the command:
-o Acquire::Check-Valid-Until=false
For example:
sudo apt-get -o Acquire::Check-Valid-Until=false update
edited Feb 8 '16 at 8:46
Tshepang
26.4k72187265
answered Aug 21 '12 at 8:23
A AA A
74662
10
This worked, but some explanation of why it did would be useful.
– Faheem Mitha
Sep 9 '14 at 23:17
2
This deactivates the check which verifies expired digital signatures, so apt will accept old and expired release keys as well.
– grin
May 31 '17 at 11:05
5
Security Warning: This answer is a work around (as asked for). However it is better to fix the mirror or point to a working one. I changed to point at httpredir.debian.org/debian and it started working again.
– ctrl-alt-delor
Jun 2 '17 at 7:36
2
you cannot switch that easily for already deprecated releases like say debian 6 where you need to use archives.debian.org to get any packages now
– Marcin Orlowski
Aug 23 '18 at 13:46
add a comment |
Add this to the command:
-o Acquire::Check-Valid-Until=false
For example:
sudo apt-get -o Acquire::Check-Valid-Until=false update
edited Feb 8 '16 at 8:46
Tshepang
26.4k72187265
answered Aug 21 '12 at 8:23
A AA A
74662
10
This worked, but some explanation of why it did would be useful.
– Faheem Mitha
Sep 9 '14 at 23:17
2
This deactivates the check which verifies expired digital signatures, so apt will accept old and expired release keys as well.
– grin
May 31 '17 at 11:05
5
Security Warning: This answer is a work around (as asked for). However it is better to fix the mirror or point to a working one. I changed to point at httpredir.debian.org/debian and it started working again.
– ctrl-alt-delor
Jun 2 '17 at 7:36
2
you cannot switch that easily for already deprecated releases like say debian 6 where you need to use archives.debian.org to get any packages now
– Marcin Orlowski
Aug 23 '18 at 13:46
add a comment |
Add this to the command:
-o Acquire::Check-Valid-Until=false
For example:
sudo apt-get -o Acquire::Check-Valid-Until=false update
edited Feb 8 '16 at 8:46
Tshepang
26.4k72187265
answered Aug 21 '12 at 8:23
A AA A
74662
Add this to the command:
-o Acquire::Check-Valid-Until=false
For example:
sudo apt-get -o Acquire::Check-Valid-Until=false update
edited Feb 8 '16 at 8:46
Tshepang
26.4k72187265
answered Aug 21 '12 at 8:23
A AA A
74662
edited Feb 8 '16 at 8:46
Tshepang
26.4k72187265
edited Feb 8 '16 at 8:46
Tshepang
26.4k72187265
edited Feb 8 '16 at 8:46
Tshepang
26.4k72187265
26.4k72187265
answered Aug 21 '12 at 8:23
A AA A
74662
answered Aug 21 '12 at 8:23
A AA A
74662
answered Aug 21 '12 at 8:23
A AA A
74662
74662
10
This worked, but some explanation of why it did would be useful.
– Faheem Mitha
Sep 9 '14 at 23:17
2
This deactivates the check which verifies expired digital signatures, so apt will accept old and expired release keys as well.
– grin
May 31 '17 at 11:05
5
Security Warning: This answer is a work around (as asked for). However it is better to fix the mirror or point to a working one. I changed to point at httpredir.debian.org/debian and it started working again.
– ctrl-alt-delor
Jun 2 '17 at 7:36
2
you cannot switch that easily for already deprecated releases like say debian 6 where you need to use archives.debian.org to get any packages now
– Marcin Orlowski
Aug 23 '18 at 13:46
add a comment |
10
This worked, but some explanation of why it did would be useful.
– Faheem Mitha
Sep 9 '14 at 23:17
2
This deactivates the check which verifies expired digital signatures, so apt will accept old and expired release keys as well.
– grin
May 31 '17 at 11:05
5
Security Warning: This answer is a work around (as asked for). However it is better to fix the mirror or point to a working one. I changed to point at httpredir.debian.org/debian and it started working again.
– ctrl-alt-delor
Jun 2 '17 at 7:36
2
you cannot switch that easily for already deprecated releases like say debian 6 where you need to use archives.debian.org to get any packages now
– Marcin Orlowski
Aug 23 '18 at 13:46
10
10
This worked, but some explanation of why it did would be useful.
– Faheem Mitha
Sep 9 '14 at 23:17
This worked, but some explanation of why it did would be useful.
– Faheem Mitha
Sep 9 '14 at 23:17
2
2
This deactivates the check which verifies expired digital signatures, so apt will accept old and expired release keys as well.
– grin
May 31 '17 at 11:05
This deactivates the check which verifies expired digital signatures, so apt will accept old and expired release keys as well.
– grin
May 31 '17 at 11:05
5
5
Security Warning: This answer is a work around (as asked for). However it is better to fix the mirror or point to a working one. I changed to point at httpredir.debian.org/debian and it started working again.
– ctrl-alt-delor
Jun 2 '17 at 7:36
Security Warning: This answer is a work around (as asked for). However it is better to fix the mirror or point to a working one. I changed to point at httpredir.debian.org/debian and it started working again.
– ctrl-alt-delor
Jun 2 '17 at 7:36
2
2
you cannot switch that easily for already deprecated releases like say debian 6 where you need to use archives.debian.org to get any packages now
– Marcin Orlowski
Aug 23 '18 at 13:46
you cannot switch that easily for already deprecated releases like say debian 6 where you need to use archives.debian.org to get any packages now
– Marcin Orlowski
Aug 23 '18 at 13:46
add a comment |
If you do not care about this check, no matter for which mirror, just create a file in /etc/apt/apt.conf.d/ (e.g. name it 10no--check-valid-until) and put the option directly in there:
Acquire::Check-Valid-Until "0";
After this, you will never be bothered again with the mentioned warning at all.
answered Feb 24 '15 at 7:24
JaleksJaleks
1,496624
1
Although the workaround itself isn't the optimal solution, I have a development box that I don't care about, so this annoyance simply gets in my way. I was able to use this answer with Ansible since I can't find any way to add the accepted answer to the action module when using ansible_pkg_mgr.
– jia103
Nov 11 '16 at 23:44
add a comment |
If you do not care about this check, no matter for which mirror, just create a file in /etc/apt/apt.conf.d/ (e.g. name it 10no--check-valid-until) and put the option directly in there:
Acquire::Check-Valid-Until "0";
After this, you will never be bothered again with the mentioned warning at all.
answered Feb 24 '15 at 7:24
JaleksJaleks
1,496624
1
Although the workaround itself isn't the optimal solution, I have a development box that I don't care about, so this annoyance simply gets in my way. I was able to use this answer with Ansible since I can't find any way to add the accepted answer to the action module when using ansible_pkg_mgr.
– jia103
Nov 11 '16 at 23:44
add a comment |
If you do not care about this check, no matter for which mirror, just create a file in /etc/apt/apt.conf.d/ (e.g. name it 10no--check-valid-until) and put the option directly in there:
Acquire::Check-Valid-Until "0";
After this, you will never be bothered again with the mentioned warning at all.
answered Feb 24 '15 at 7:24
JaleksJaleks
1,496624
If you do not care about this check, no matter for which mirror, just create a file in /etc/apt/apt.conf.d/ (e.g. name it 10no--check-valid-until) and put the option directly in there:
Acquire::Check-Valid-Until "0";
After this, you will never be bothered again with the mentioned warning at all.
answered Feb 24 '15 at 7:24
JaleksJaleks
1,496624
edited Apr 29 '18 at 9:17
answered Feb 24 '15 at 7:24
JaleksJaleks
1,496624
answered Feb 24 '15 at 7:24
JaleksJaleks
1,496624
answered Feb 24 '15 at 7:24
JaleksJaleks
1,496624
1,496624
1
Although the workaround itself isn't the optimal solution, I have a development box that I don't care about, so this annoyance simply gets in my way. I was able to use this answer with Ansible since I can't find any way to add the accepted answer to the action module when using ansible_pkg_mgr.
– jia103
Nov 11 '16 at 23:44
add a comment |
1
Although the workaround itself isn't the optimal solution, I have a development box that I don't care about, so this annoyance simply gets in my way. I was able to use this answer with Ansible since I can't find any way to add the accepted answer to the action module when using ansible_pkg_mgr.
– jia103
Nov 11 '16 at 23:44
1
1
Although the workaround itself isn't the optimal solution, I have a development box that I don't care about, so this annoyance simply gets in my way. I was able to use this answer with Ansible since I can't find any way to add the accepted answer to the action module when using ansible_pkg_mgr.
– jia103
Nov 11 '16 at 23:44
Although the workaround itself isn't the optimal solution, I have a development box that I don't care about, so this annoyance simply gets in my way. I was able to use this answer with Ansible since I can't find any way to add the accepted answer to the action module when using ansible_pkg_mgr.
– jia103
Nov 11 '16 at 23:44
add a comment |
The release files have a valid-until entry, e.g. Valid-Until: Thu, 07 Oct 2010 08:17:56 UTC
If the release file isn't valid anymore, you should run debmirror again to check if there are any changes in the repository. One change will be the release file and you will get a new validity for it.
You could easily automate this with a crontab entry.
answered Sep 30 '10 at 11:42
echoxechox
13.1k43953
Thanks for that one. I should have looked inside that file before asking. Curiously though, is this a new thing? It didn't happen before (but once).
– Tshepang
Sep 30 '10 at 11:58
I don't use debian really often at the moment, but maybe they just changed the release file cycles to a shorter date...
– echox
Sep 30 '10 at 12:03
add a comment |
The release files have a valid-until entry, e.g. Valid-Until: Thu, 07 Oct 2010 08:17:56 UTC
If the release file isn't valid anymore, you should run debmirror again to check if there are any changes in the repository. One change will be the release file and you will get a new validity for it.
You could easily automate this with a crontab entry.
answered Sep 30 '10 at 11:42
echoxechox
13.1k43953
Thanks for that one. I should have looked inside that file before asking. Curiously though, is this a new thing? It didn't happen before (but once).
– Tshepang
Sep 30 '10 at 11:58
I don't use debian really often at the moment, but maybe they just changed the release file cycles to a shorter date...
– echox
Sep 30 '10 at 12:03
add a comment |
The release files have a valid-until entry, e.g. Valid-Until: Thu, 07 Oct 2010 08:17:56 UTC
If the release file isn't valid anymore, you should run debmirror again to check if there are any changes in the repository. One change will be the release file and you will get a new validity for it.
You could easily automate this with a crontab entry.
answered Sep 30 '10 at 11:42
echoxechox
13.1k43953
The release files have a valid-until entry, e.g. Valid-Until: Thu, 07 Oct 2010 08:17:56 UTC
If the release file isn't valid anymore, you should run debmirror again to check if there are any changes in the repository. One change will be the release file and you will get a new validity for it.
You could easily automate this with a crontab entry.
answered Sep 30 '10 at 11:42
echoxechox
13.1k43953
answered Sep 30 '10 at 11:42
echoxechox
13.1k43953
answered Sep 30 '10 at 11:42
echoxechox
13.1k43953
answered Sep 30 '10 at 11:42
echoxechox
13.1k43953
13.1k43953
Thanks for that one. I should have looked inside that file before asking. Curiously though, is this a new thing? It didn't happen before (but once).
– Tshepang
Sep 30 '10 at 11:58
I don't use debian really often at the moment, but maybe they just changed the release file cycles to a shorter date...
– echox
Sep 30 '10 at 12:03
add a comment |
Thanks for that one. I should have looked inside that file before asking. Curiously though, is this a new thing? It didn't happen before (but once).
– Tshepang
Sep 30 '10 at 11:58
I don't use debian really often at the moment, but maybe they just changed the release file cycles to a shorter date...
– echox
Sep 30 '10 at 12:03
Thanks for that one. I should have looked inside that file before asking. Curiously though, is this a new thing? It didn't happen before (but once).
– Tshepang
Sep 30 '10 at 11:58
Thanks for that one. I should have looked inside that file before asking. Curiously though, is this a new thing? It didn't happen before (but once).
– Tshepang
Sep 30 '10 at 11:58
I don't use debian really often at the moment, but maybe they just changed the release file cycles to a shorter date...
– echox
Sep 30 '10 at 12:03
I don't use debian really often at the moment, but maybe they just changed the release file cycles to a shorter date...
– echox
Sep 30 '10 at 12:03
add a comment |
Some of the mirrors out there might have stale files. This happened to me recently, and it was in also tied to the caching server I'm using (apt-cacher-ng) which tries to save bandwidth by redirecting the repositories for same archive to a single entity (in my case if was a Hungarian mirror). Direct updates through German mirror worked ok, for example. Try changing the mirror you're using. In case you're using apt-cacher-ng, you'll need to do something in the line of changing the following file's contents:
- /etc/apt-cacher-ng/backends_debian
- /etc/apt-cacher-ng/backends_debvol
After that you should also restart apt-cacher-ng for changes to take effect.
edited Aug 10 '15 at 13:35
Tshepang
26.4k72187265
Note that I was asking for a workaround, not why this was happening (good answer though). In this case I was, knowingly, having a stale repository.
– Tshepang
May 13 '11 at 12:44
add a comment |
Some of the mirrors out there might have stale files. This happened to me recently, and it was in also tied to the caching server I'm using (apt-cacher-ng) which tries to save bandwidth by redirecting the repositories for same archive to a single entity (in my case if was a Hungarian mirror). Direct updates through German mirror worked ok, for example. Try changing the mirror you're using. In case you're using apt-cacher-ng, you'll need to do something in the line of changing the following file's contents:
- /etc/apt-cacher-ng/backends_debian
- /etc/apt-cacher-ng/backends_debvol
After that you should also restart apt-cacher-ng for changes to take effect.
edited Aug 10 '15 at 13:35
Tshepang
26.4k72187265
Note that I was asking for a workaround, not why this was happening (good answer though). In this case I was, knowingly, having a stale repository.
– Tshepang
May 13 '11 at 12:44
add a comment |
Some of the mirrors out there might have stale files. This happened to me recently, and it was in also tied to the caching server I'm using (apt-cacher-ng) which tries to save bandwidth by redirecting the repositories for same archive to a single entity (in my case if was a Hungarian mirror). Direct updates through German mirror worked ok, for example. Try changing the mirror you're using. In case you're using apt-cacher-ng, you'll need to do something in the line of changing the following file's contents:
- /etc/apt-cacher-ng/backends_debian
- /etc/apt-cacher-ng/backends_debvol
After that you should also restart apt-cacher-ng for changes to take effect.
edited Aug 10 '15 at 13:35
Tshepang
26.4k72187265
Some of the mirrors out there might have stale files. This happened to me recently, and it was in also tied to the caching server I'm using (apt-cacher-ng) which tries to save bandwidth by redirecting the repositories for same archive to a single entity (in my case if was a Hungarian mirror). Direct updates through German mirror worked ok, for example. Try changing the mirror you're using. In case you're using apt-cacher-ng, you'll need to do something in the line of changing the following file's contents:
- /etc/apt-cacher-ng/backends_debian
- /etc/apt-cacher-ng/backends_debvol
After that you should also restart apt-cacher-ng for changes to take effect.
edited Aug 10 '15 at 13:35
Tshepang
26.4k72187265
edited Aug 10 '15 at 13:35
Tshepang
26.4k72187265
edited Aug 10 '15 at 13:35
Tshepang
26.4k72187265
edited Aug 10 '15 at 13:35
Tshepang
26.4k72187265
26.4k72187265
answered Feb 22 '11 at 8:54
user4973
Note that I was asking for a workaround, not why this was happening (good answer though). In this case I was, knowingly, having a stale repository.
– Tshepang
May 13 '11 at 12:44
add a comment |
Note that I was asking for a workaround, not why this was happening (good answer though). In this case I was, knowingly, having a stale repository.
– Tshepang
May 13 '11 at 12:44
Note that I was asking for a workaround, not why this was happening (good answer though). In this case I was, knowingly, having a stale repository.
– Tshepang
May 13 '11 at 12:44
Note that I was asking for a workaround, not why this was happening (good answer though). In this case I was, knowingly, having a stale repository.
– Tshepang
May 13 '11 at 12:44
add a comment |
This can also happen if your system date/time is wrong. I fixed it by correcting my local time before doing the update.
edited Sep 19 '18 at 20:51
Michael Mrozek♦
62.2k29193213
answered Sep 19 '18 at 20:08
MarrekNožkaMarrekNožka
311
@AnthonyGeoghegan It does for me. This is the only thing that worked in the end.
– Martin Vseticka
Jan 30 at 22:28
1
@MartinVseticka You’re right. I made that comment when I came across this answer in one of the review queues after the system flagged it for moderation. The original wording (before Michael edited it) was far less useful.
– Anthony Geoghegan
Jan 31 at 10:13
add a comment |
This can also happen if your system date/time is wrong. I fixed it by correcting my local time before doing the update.
edited Sep 19 '18 at 20:51
Michael Mrozek♦
62.2k29193213
answered Sep 19 '18 at 20:08
MarrekNožkaMarrekNožka
311
@AnthonyGeoghegan It does for me. This is the only thing that worked in the end.
– Martin Vseticka
Jan 30 at 22:28
1
@MartinVseticka You’re right. I made that comment when I came across this answer in one of the review queues after the system flagged it for moderation. The original wording (before Michael edited it) was far less useful.
– Anthony Geoghegan
Jan 31 at 10:13
add a comment |
This can also happen if your system date/time is wrong. I fixed it by correcting my local time before doing the update.
edited Sep 19 '18 at 20:51
Michael Mrozek♦
62.2k29193213
answered Sep 19 '18 at 20:08
MarrekNožkaMarrekNožka
311
This can also happen if your system date/time is wrong. I fixed it by correcting my local time before doing the update.
edited Sep 19 '18 at 20:51
Michael Mrozek♦
62.2k29193213
answered Sep 19 '18 at 20:08
MarrekNožkaMarrekNožka
311
edited Sep 19 '18 at 20:51
Michael Mrozek♦
62.2k29193213
edited Sep 19 '18 at 20:51
Michael Mrozek♦
62.2k29193213
edited Sep 19 '18 at 20:51
Michael Mrozek♦
62.2k29193213
62.2k29193213
answered Sep 19 '18 at 20:08
MarrekNožkaMarrekNožka
311
answered Sep 19 '18 at 20:08
MarrekNožkaMarrekNožka
311
answered Sep 19 '18 at 20:08
MarrekNožkaMarrekNožka
311
311
@AnthonyGeoghegan It does for me. This is the only thing that worked in the end.
– Martin Vseticka
Jan 30 at 22:28
1
@MartinVseticka You’re right. I made that comment when I came across this answer in one of the review queues after the system flagged it for moderation. The original wording (before Michael edited it) was far less useful.
– Anthony Geoghegan
Jan 31 at 10:13
add a comment |
@AnthonyGeoghegan It does for me. This is the only thing that worked in the end.
– Martin Vseticka
Jan 30 at 22:28
1
@MartinVseticka You’re right. I made that comment when I came across this answer in one of the review queues after the system flagged it for moderation. The original wording (before Michael edited it) was far less useful.
– Anthony Geoghegan
Jan 31 at 10:13
@AnthonyGeoghegan It does for me. This is the only thing that worked in the end.
– Martin Vseticka
Jan 30 at 22:28
@AnthonyGeoghegan It does for me. This is the only thing that worked in the end.
– Martin Vseticka
Jan 30 at 22:28
1
1
@MartinVseticka You’re right. I made that comment when I came across this answer in one of the review queues after the system flagged it for moderation. The original wording (before Michael edited it) was far less useful.
– Anthony Geoghegan
Jan 31 at 10:13
@MartinVseticka You’re right. I made that comment when I came across this answer in one of the review queues after the system flagged it for moderation. The original wording (before Michael edited it) was far less useful.
– Anthony Geoghegan
Jan 31 at 10:13
add a comment |
I removed /var/lib/apt/* and rerun apt-get update, and it works!
edited Jan 12 '15 at 20:40
HalosGhost
3,78392236
answered Jan 12 '15 at 20:24
PatrickPatrick
1643
I do that for a completely different error, and it works for that one. This error is completely irrelevant.
– snetch
Jul 10 '17 at 17:21
add a comment |
I removed /var/lib/apt/* and rerun apt-get update, and it works!
edited Jan 12 '15 at 20:40
HalosGhost
3,78392236
answered Jan 12 '15 at 20:24
PatrickPatrick
1643
I do that for a completely different error, and it works for that one. This error is completely irrelevant.
– snetch
Jul 10 '17 at 17:21
add a comment |
I removed /var/lib/apt/* and rerun apt-get update, and it works!
edited Jan 12 '15 at 20:40
HalosGhost
3,78392236
answered Jan 12 '15 at 20:24
PatrickPatrick
1643
I removed /var/lib/apt/* and rerun apt-get update, and it works!
edited Jan 12 '15 at 20:40
HalosGhost
3,78392236
answered Jan 12 '15 at 20:24
PatrickPatrick
1643
edited Jan 12 '15 at 20:40
HalosGhost
3,78392236
edited Jan 12 '15 at 20:40
HalosGhost
3,78392236
edited Jan 12 '15 at 20:40
HalosGhost
3,78392236
3,78392236
answered Jan 12 '15 at 20:24
PatrickPatrick
1643
answered Jan 12 '15 at 20:24
PatrickPatrick
1643
answered Jan 12 '15 at 20:24
PatrickPatrick
1643
1643
I do that for a completely different error, and it works for that one. This error is completely irrelevant.
– snetch
Jul 10 '17 at 17:21
add a comment |
I do that for a completely different error, and it works for that one. This error is completely irrelevant.
– snetch
Jul 10 '17 at 17:21
I do that for a completely different error, and it works for that one. This error is completely irrelevant.
– snetch
Jul 10 '17 at 17:21
I do that for a completely different error, and it works for that one. This error is completely irrelevant.
– snetch
Jul 10 '17 at 17:21
add a comment |
The mirror might not be expired.
Rather something else on your system might be messed up. Try this:
1) Temporarily comment out related lines from from /etc/apt/sources.list, or /etc/apt/source.list.d/*. For example after I commented out the following two lines, my error went away, (with the consequence that these archives were temporarily not used for reloads):
deb http://security.debian.org/ stretch/updates non-free contrib main
deb http://mirrors.ocf.berkeley.edu/debian/ stretch-updates main contrib non-free
2) Open synaptic and reload, or probably sudo apt-get update would also work.
3) Comment these lines back in.
4) Repeat step 2.
Fixed this for me. I'm guessing my apt cache got a bad date in it.
My problem occurred after restoring my / (root) and /var filesystems from btrfs snapshots to help fix a package install problem that occurred. The exact error message that I was getting was:
Release file for
http://mirrors.ocf.berkeley.edu/debian/dists/stretch-updates/InRelease
is expired (invalid since 5d 4h 50min 18s). Updates for this
repository will not be applied. Release file for
http://security.debian.org/dists/stretch/updates/InRelease is expired
(invalid since 2d 2h 52min 43s). Updates for this repository will not
be applied.
answered Feb 19 '18 at 0:12
Elliptical viewElliptical view
6231623
add a comment |
The mirror might not be expired.
Rather something else on your system might be messed up. Try this:
1) Temporarily comment out related lines from from /etc/apt/sources.list, or /etc/apt/source.list.d/*. For example after I commented out the following two lines, my error went away, (with the consequence that these archives were temporarily not used for reloads):
deb http://security.debian.org/ stretch/updates non-free contrib main
deb http://mirrors.ocf.berkeley.edu/debian/ stretch-updates main contrib non-free
2) Open synaptic and reload, or probably sudo apt-get update would also work.
3) Comment these lines back in.
4) Repeat step 2.
Fixed this for me. I'm guessing my apt cache got a bad date in it.
My problem occurred after restoring my / (root) and /var filesystems from btrfs snapshots to help fix a package install problem that occurred. The exact error message that I was getting was:
Release file for
http://mirrors.ocf.berkeley.edu/debian/dists/stretch-updates/InRelease
is expired (invalid since 5d 4h 50min 18s). Updates for this
repository will not be applied. Release file for
http://security.debian.org/dists/stretch/updates/InRelease is expired
(invalid since 2d 2h 52min 43s). Updates for this repository will not
be applied.
answered Feb 19 '18 at 0:12
Elliptical viewElliptical view
6231623
add a comment |
The mirror might not be expired.
Rather something else on your system might be messed up. Try this:
1) Temporarily comment out related lines from from /etc/apt/sources.list, or /etc/apt/source.list.d/*. For example after I commented out the following two lines, my error went away, (with the consequence that these archives were temporarily not used for reloads):
deb http://security.debian.org/ stretch/updates non-free contrib main
deb http://mirrors.ocf.berkeley.edu/debian/ stretch-updates main contrib non-free
2) Open synaptic and reload, or probably sudo apt-get update would also work.
3) Comment these lines back in.
4) Repeat step 2.
Fixed this for me. I'm guessing my apt cache got a bad date in it.
My problem occurred after restoring my / (root) and /var filesystems from btrfs snapshots to help fix a package install problem that occurred. The exact error message that I was getting was:
Release file for
http://mirrors.ocf.berkeley.edu/debian/dists/stretch-updates/InRelease
is expired (invalid since 5d 4h 50min 18s). Updates for this
repository will not be applied. Release file for
http://security.debian.org/dists/stretch/updates/InRelease is expired
(invalid since 2d 2h 52min 43s). Updates for this repository will not
be applied.
answered Feb 19 '18 at 0:12
Elliptical viewElliptical view
6231623
The mirror might not be expired.
Rather something else on your system might be messed up. Try this:
1) Temporarily comment out related lines from from /etc/apt/sources.list, or /etc/apt/source.list.d/*. For example after I commented out the following two lines, my error went away, (with the consequence that these archives were temporarily not used for reloads):
deb http://security.debian.org/ stretch/updates non-free contrib main
deb http://mirrors.ocf.berkeley.edu/debian/ stretch-updates main contrib non-free
2) Open synaptic and reload, or probably sudo apt-get update would also work.
3) Comment these lines back in.
4) Repeat step 2.
Fixed this for me. I'm guessing my apt cache got a bad date in it.
My problem occurred after restoring my / (root) and /var filesystems from btrfs snapshots to help fix a package install problem that occurred. The exact error message that I was getting was:
Release file for
http://mirrors.ocf.berkeley.edu/debian/dists/stretch-updates/InRelease
is expired (invalid since 5d 4h 50min 18s). Updates for this
repository will not be applied. Release file for
http://security.debian.org/dists/stretch/updates/InRelease is expired
(invalid since 2d 2h 52min 43s). Updates for this repository will not
be applied.
answered Feb 19 '18 at 0:12
Elliptical viewElliptical view
6231623
answered Feb 19 '18 at 0:12
Elliptical viewElliptical view
6231623
answered Feb 19 '18 at 0:12
Elliptical viewElliptical view
6231623
answered Feb 19 '18 at 0:12
Elliptical viewElliptical view
6231623
6231623
add a comment |
add a comment |
Not sure whether its related with Jessie current issue (https://lists.debian.org/debian-devel-announce/2019/03/msg00006.html) or not. but for those got a same error even already used "sudo apt-get -o Acquire::Check-Valid-Until=false update" and still occurred a same issue, can try this instead "echo 'Acquire::Check-Valid-Until no;' > /etc/apt/apt.conf.d/99no-check-valid-until"
It works for me :)
Thanks!
answered 13 mins ago
Alex ChandraAlex Chandra
11
New contributor
Alex Chandra is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Not sure whether its related with Jessie current issue (https://lists.debian.org/debian-devel-announce/2019/03/msg00006.html) or not. but for those got a same error even already used "sudo apt-get -o Acquire::Check-Valid-Until=false update" and still occurred a same issue, can try this instead "echo 'Acquire::Check-Valid-Until no;' > /etc/apt/apt.conf.d/99no-check-valid-until"
It works for me :)
Thanks!
answered 13 mins ago
Alex ChandraAlex Chandra
11
New contributor
Alex Chandra is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Not sure whether its related with Jessie current issue (https://lists.debian.org/debian-devel-announce/2019/03/msg00006.html) or not. but for those got a same error even already used "sudo apt-get -o Acquire::Check-Valid-Until=false update" and still occurred a same issue, can try this instead "echo 'Acquire::Check-Valid-Until no;' > /etc/apt/apt.conf.d/99no-check-valid-until"
It works for me :)
Thanks!
answered 13 mins ago
Alex ChandraAlex Chandra
11
New contributor
Alex Chandra is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Not sure whether its related with Jessie current issue (https://lists.debian.org/debian-devel-announce/2019/03/msg00006.html) or not. but for those got a same error even already used "sudo apt-get -o Acquire::Check-Valid-Until=false update" and still occurred a same issue, can try this instead "echo 'Acquire::Check-Valid-Until no;' > /etc/apt/apt.conf.d/99no-check-valid-until"
It works for me :)
Thanks!
answered 13 mins ago
Alex ChandraAlex Chandra
11
New contributor
Alex Chandra is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 13 mins ago
Alex ChandraAlex Chandra
11
New contributor
Alex Chandra is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 13 mins ago
Alex ChandraAlex Chandra
11
answered 13 mins ago
Alex ChandraAlex Chandra
11
11
New contributor
Alex Chandra is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Alex Chandra is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Alex Chandra is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f2544%2fhow-to-work-around-release-file-expired-problem-on-a-local-mirror%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
4
Security Warning: This question asks for a work around. However it is better to fix the mirror or point to a working one. I changed to point at httpredir.debian.org/debian and it started working again.
– ctrl-alt-delor
Jun 2 '17 at 7:37
Switch to a different mirror and it'll work.
– Patrick Mutwiri
Jul 21 '18 at 12:49
2
What is "better" depends on what your goals are. If your goal is to get the latest packages from Debian then changing mirror is the right soloution. If your goal is to use the older mirror that you have locally so you can get on with your work where Internet is unavailable or expensive then turning off the expiry check is the right solution. If your goal is to update to a specific older version of the repo for bug triage reasons then again turning off the expiry check is the right solution.
– plugwash
Sep 20 '18 at 19:11