- This topic has 6 replies, 5 voices, and was last updated Apr 7-8:16 pm by ctcx.
-
Posts
-
ctcx
Today, and even just now, I cannot run “apt update” anymore. I get this error:
E: Release file for http://security.debian.org/dists/bullseye-security/InRelease is not valid yet (invalid for another 40min 40s). Updates for this repository will not be applied.
The problem is, that min/sec counter not always goes down. Sometimes it does, some others it just increases. It seems to get worse if I poweroff and on again.
I already tried sync-ing RTC with windows time service (this is a dual boot)
I already tried “rm -r /var/{cache,lib}/apt/*” and apt update againNothing works.
What on hell is going on here?
anticapitalista
Change your repo or wait 40 minutes
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
And how can I properly change the repo in this case?
sybok
This type of “invalid” may also indicate your system time may be off.
Changing repository (already discussed on the forum elsewhere or in some tutorial videos) is pretty simple:
[Applications -> System -> ] Control Centre -> Software -> Repo ManagerXunzi_23
Most cases are caused by wdoze in dual boot setups.
I already tried sync-ing RTC with windows time service
Windows generaly sets hardware clock to UTC. That depending on user location and
offset to local time may cause you to be behind the time at the repository.You will probably then get the release file warning. i think depending on
some expected time tolerances in the repository server setup.You can not just wait 40 minutes as time is a moving target.
To get back to sanity set time in BIOS Manualy.- This reply was modified 3 weeks, 6 days ago by Xunzi_23.
- This reply was modified 3 weeks, 6 days ago by Xunzi_23.
- This reply was modified 3 weeks, 6 days ago by Xunzi_23.
BobC
Yes, wrong time setting is usually the cause. If you are connected to the internet, in control centre, system, set date and time, there is an option to set your time from the internet.
If you installed it, my guess is your system time is off, or you took the wrong choice on the “System uses local time” selection
Both in Windows and AntiX time zone is correctly set according to where I am.
Also, to boot AntiX I have to set hwclock=local boot option always due to the Windows installation.
I have noticed that this whole problem has always happened to me actually daily circa between 19:00 and 21:00 hrs UTC, with the very same repo and sometimes other ones.
It’s way too bothersome and not fair…Again, what’s happening?
EDIT: the counter seems to increase if I boot Windows, then AntiX again…
- You must be logged in to reply to this topic.
