On 28/10/2021 15.36, Darryl Gregorash wrote:
On 2021-10-28 6:37 a.m., Carlos E. R. wrote:
...
The release version number is in the overwhelming majority of repo urls you will ever encounter. If you leave it alone, you will always need to change it some months away == so why not do it right away as a matter of habit?
I may. I may not remember the exact syntax at that moment and postpone.
Will everybody?
The point is, we have added more work for the admin :-p
I submit it's a lot less work than running sed on the cli with every upgrade, then copying the new file versions over the LAN to a multiplicity of client installations.
I always did and will continue doing, looking at the repo list carefully before doing an upgrade - example: grep "15.2\" *repo And probably edit the files that need modification, not paste the sed concoction which I would first have to find in the wiki or my notes. Also, as each machine has a different repo list, I never copy the files from one installation to another. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)