kfowler

Ok, fair enough. I hesitated taking that step, partly because it seemed I needed to do it manually on every system (I have a LOT of systems in remote locations), and partly because I didn't want to risk something going wrong, requiring me to travel to those remote locations. But I probably should find some time to experiment with it and start upgrading my systems. Thanks again

First of all, thank you - I no longer get errors on "apt update" when I have the /etc/apt/sources.list.d/armbian.list content un-commented for my stretch systems. Much appreciated. One thing I expected to get with this was package updates related to armbian versions, such as: linux-dtb-next-sunxi/now 5.83 armhf [installed,local] linux-image-next-sunxi/now 5.83 armhf [installed,local] linux-libc-dev/now 5.70 armhf [installed,local] linux-stretch-root-next-orangepiplus2e/now 5.83 armhf [installed,local] linux-u-boot-orangepiplus2e-next/now 5.83 armhf [installed,local] To be clear(er), I initially install with the Armbian 5.83 image (the last one with the 4.19.x kernel, specifically 4.19.38-sunxi). Then I apt update/upgrade. This had brought my earlier systems up to Armbian 5.90 with kernel 4.19.62-sunxi. But even with the stretch support re-added to the repo server, that is no longer happening. It is likely I am confused about where those linux packages were coming from, and perhaps I'm splitting hairs about dealing with two old kernel versions. But I'd thought it was worth asking about. Thanks again for the timely response Kevin

I have a large number of distributed orangepi (plus2e and zero) systems running Armbian stretch, and am building a few more. I do not want to attempt remote dist upgrades to buster, because if there are upgrade failures it may result in downtime, or worse - require a trip to the site. I also want all my systems on roughly the same version to simplify support issues. I also understand you do not want to support stretch into the future; but, could the "last" versions of your stretch packages still be available from your package server, even though they are no longer updated/maintained? This would allow me to set up new stretch systems to match the existing systems in the field. I have also had to comment out the /etc/apt/sources.list.d/armbian.list content so that 'apt update' does not error out on all the deployed systems. The day will come where I will devise some reliable procedure to upgrade all deployed systems to a current distribution/kernel; however, I do not currently have the resources to make that happen - something that I expect you guys at Armbian can appreciate. Thank you, Kevin