linux-libre mirrors are not updating
- Anmelden oder Registrieren um Kommentare zu schreiben
I am not sure why, but as far as I can tell the linux-libre mirrors are not updating themselves. It might be that linux-libre.fsfla.org is having network issues, as I find it very slow too.
So when I try to apt update with freesh sources it would get Ign messages. Are others seeing similar issues?
I am a translator!
I am not sure whether it is about mirrors not updating but I see Ign messages as well, and the download can be really slow. Besides, I am in Europe and it looks like it tends to download from a mirror in Australia, which does not look like a great idea. So I was wondering whether it is such a good idea to use the mirror.txt file that is being installed by default.
Since I am using linux-libre from the freesh repository on 2 computers, I was thinking that perhaps I could setup a private mirror, but I am not sure how to do that. I saw that Trisquel suggests a service with rsync for that (and I am considering to setup a mirror as well). If I can do a mirror for linux-libre and if it works, I could also make it public, either at home or using a VPS that has unlimited traffic and that I mostly use for Jitsi not that frequently.
I confirm that I used to also get slow speeds, and today I got a "mirror://mirror.cyberbits.eu/linux-libre/freesh/mirrors.txt freesh Release no longer holds a Release file" kinda message.
Not sure how to upgrade to a later kernel anymore.
Run this command in the Terminal to change to linux-libre.fsfla.org/pub/linux-libre/freesh/mirrors.txt
sudo sed -i 's|mirror://mirror.cyberbits.eu/linux-libre/freesh/mirrors.txt|mirror://linux-libre.fsfla.org/pub/linux-libre/freesh/mirrors.txt|' /etc/apt/sources.list.d/freesh.sources
Thanks, that seems to have worked fine. I was not aware of the change on the URL.
After upgrading, I am now on 6.16.5-gnu
Today, the latest GNU Linux-libre version is 6.16.7
Indeed. After couple reboots and running "sudo apt autoremove" that's the result in uname -r
Hopefully it will stay that way (in another thread I mentioned my system sometimes boots with the older generic kernel, appears to be a random behavior).
Thanks!