Linux-libre repo failing to fetch during apt update
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
For the last 3 days or so, I've been getting this error message every time I run an apt update and upgrade:
> W: Failed to fetch mirror://linux-libre.fsfla.org/pub/linux-libre/freesh/mirrors.txt/dists/freesh/InRelease Temporary failure resolving 'linux-libre.gnulinux.si' [Mirror: http://linux-libre.gnulinux.si/freesh/]
Obviously, I'm using kernels from jxself's Linux-Libre repo, instead of the standard Trisquel kernels. All the other software sources are queried successfully and updates are being installed from them. Any idea why this is happening, or what I can do to fix it?
Thanks MagicBanana. I will try changing mirrors, as you suggest. But the fact that both the gnulinux.si and fsfla.org mirrors are down, yet both still on the mirrors list, suggests there may a deeper problem here. I'm a bit concerned that jxself hasn't responded on that thread at all. Has anyone heard from him recently?
I have removed that mirror.
> I'm a bit concerned that jxself hasn't responded on that thread at all.
I don't read all threads on the forums and didn't know that "Problems after upgrade" had anything to do with my APT repository.
The other part I find concerning is that in both of the threads there was no suggestion to contact me to report the problem. If there are problems people should actually _tell me_ (i.e., pop open an email program and write in) - I can't promise to see messages posted elsewhere.
Hi jxself, it's a great relief to see you respond here. I just want to clarify that my concern was for your health and wellbeing, in the context of a global pandemic. My comments were not intended in any way as an attack on your competence or diligence, which are consistently beyond reproach.
> didn't know that "Problems after upgrade" had anything to do with my APT repository.
No, I didn't either, or I wouldn't have opened a second thread on the topic. You're certainly not obliged or expected to read every thread on these forums (who could?). I guess I've just had the experience of you being a regular here since I first turned up, so I assumed (unfairly I admit) that someone who has out-of-band contact with you would draw your attention to forum threads involving your APT repo, if you didn't come across them yourself.
> The other part I find concerning is that in both of the threads there was no suggestion to contact me to report the problem.
Fair point.
FWIW I posted on the Trisquel forums for help first, because I figure you're a busy person (technically skilled people usually are) and I didn't want to bother you over what could have been my own user errors. If I hadn't found a solution here, contacting you directly would have been my next step. In hindsight, once I found my stopgap solution, contacting you directly to tell you that one of your APT repo mirrors had failed would have been the responsible thing to do.
I have tried opening 'Software and Updates' and changing the URL to a couple of URLs listed here:
https://linux-libre.fsfla.org/pub/linux-libre/freesh/mirrors.txt
In both cases I got an error message:
> E: The repository 'mirror://ftp.linux.org.tr/linux-libre/freesh freesh Release' does not have a Release file.
> N: Updating from such a repository can't be done securely, and is therefore disabled by default.
I'm assuming this is probably because I'm not following the correct procedure for changing mirrors. Is this documented anywhere?
OK, having had a more careful looks at the information here:
https://jxself.org/linux-libre/
... I realize that fsfla.org is not down, it's successfully redirecting my package manager to a mirror that *is* down. I also realized that the mistake I made was to leave "mirror://" before the URL of the mirror I was trying to switch to. I replaced the URI beginning with "mirror://" with the full URL of the mirror and it ran apt update successfully and downloaded a new kernel image when I ran apt upgrade.
Thanks again MagicBanana for pointing me in the right direction.
- Vous devez vous identifier ou créer un compte pour écrire des commentaires