Re: old entries in sources.list?
On 2025-06-20 22:45, Greg Wooledge wrote:
As that was a suggestion following my remark I'll add some points to
what I already posted, because I think testing is a bit different to
stable in this respect. Just to make sure others are aware of that.
There are some issues with this.
* Don't use the word "stable" in sources.list, because it points to a
moving target. When a new stable occurs, "stable" will point to the
next release, and that is a VERY BAD IDEA. You don't want a surprise
partial upgrade to occur. Release upgrades require planning.
Agreed, but I don't think that argument is valid for testing. Which is
what I am using. Testing is more of a rolling release. Stable is not.
And yes, I know testing can bring its own issues with it. I am fully
prepared to resolve them when they occur. But over the last 30 years
those were just minor issues that were easily solved.
* You're missing the non-free-firmware section which most users will
need for hardware support.
Yes, in the example given for stable that is true. I my case I included
the whole shebang:
main contrib non-free non-free-firmware
for testing and testing-security
That might not be to everyone's tastes though.
* You're missing the security update source, which almost everyone will
want, unless their system is un-networked during normal operation,
and even then, they might still want security updates periodically.
Agreed.
Grx HdV
Reply to: