I never thought I had to remove those since I figured they wouldn't change, or that the raspi servers being down wouldn't cause the apt-get update to require user intervention. We still had the raspi repos in the sources list but we've locked all package versions to the current ones except for the apt server that serves the latest version of our application. Well sure, but users think it's broken because our app reports an error. ![]() When what you mean is that they will no longer update. It's just a name thing, dist-upgrade was misleading because the distribution (wheezy/jessie/stretch/buster/bullseye) actually remains the same, there is no automatic cross-distribution upgrade in apt. It should not matter, but note that apt full-upgrade has replaced apt dist-upgrade. It is only the RPi specific updates that cease - RPT do not have the (human) bandwidth to support two versions. In the interim, will any Debian Buster updates (presumably largely security-related) be available from the Raspberry Pi Debian Buster repository, or will I need to go direct to the Debian repositories for these.Īgain, looking at the precedents, security (and other) updates from Debian will be echoed in the RPiOS repository. I won't be moving to Bullseye for a couple of months (after it is released) on my 'workhorse' Pi, since I will have a fair amount of configuration and testing to do before I can do this. I share the OP's surprise that there were no available updates after (in my case) 2 weeks since my last apt dist-upgrade. ![]() The normal mantra will continue to update systems within the original version, but from past history RPT will not continue to provide updates, so only the Debian updates will apply.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |