Re: Stable and testing together?
On Sat, May 13, 2023 at 11:28:24AM +0200, Hans wrote:
> Hi folks,
>
> there is a question, which is in my mind for many years.
>
> Is there any reason, why not using oldstable, stable and testing together?
>
Yes: wiki.debian.org has https://wiki.debian.org/DontBreakDebian#Advice_For_New_Users_On_Not_Breaking_Their_Debian_System
> I am asking this, because sometimes I need packages, whcih are no more in
> testing or stable (for example an older kernel, which is capable to run on my
> hardware and supports NVidia drivers), or maybe the kernel is from stable, but
> the Nvidia driver (in my example) is no more in the stable or testing repo. Or
> some needed software is fiully disappeared from testing or stable.
>
If you know *exactly* what you have and what you are doing, this is feasible.
If not, it is a recipe for problems the first time you run "apt-get update"
- are you running stable any more? No, you're likely to be running testing.
> In the past, I never got into problems, having "stable" and "testing" together
> in my sources.list. I always either get the newest versions from testing or I
> have to install the version in stable. This is ok for me.
>
You get the newest versions in testing and may then need to downgrade - which
is not supported.
> Also some packages I personally need, which are no more in testing but in
> stable can be installed and run without any problems.
>
> Yes, it is clear for me, that I might need to install stuff, not needed in
> pure testing (like some libs, old java, old compiler versions whatever), but I
> suppose, this is the price I have to pay.
>
> I know, from the security side that should not me accepted (KISS priciple),
> but what can one do, if either the developers can not switch to new libs or it
> is technically not possible at all?
>
Security support is another one: which distribution are you running?
> So, do you see any more problems, I missed somehow? Or is it ok from your
> view, running testing and stable entries in the sources.list together?
>
In one situation, and one situation only in my opinion, you can do this.
When testing is frozen preparatory to release, it is feasible to run
testing and then follow it through to stable as it gets released on the
day. Do *not* pin to testing or stable as the release names: always use
the codenames - that way, surprises are avoided :)
So today, for example, it would be appropriate to upgrade to bookworm given
that release is barely a month away. As ever, before updating, bring the prior
release up to date. Change sources list. Read release notes or other
information as available.
> Thanks for reading this! And I am looking forward to the next release in June.
>
> Best regards
>
> Hans
>
>
With every good wish, as ever,
Andy Cater
Reply to: