|
|
|
|
|
by hiq
1231 days ago
|
|
I just pin to a specific code name (version) instead of a state (such as testing), e.g. right now I'm using bookworm which happens to be testing, and I'll still be using it for a while once it's been declared stable. If I feel like I'd want to upgrade some packages that are available in the next testing, or I can't install some specific package from unstable because it requires an update for a big library (often libc6), I update to the next testing. I think it's better to avoid pinning to testing since it gets a lot of updates right after a stable promotion (after the package unfreeze), which you probably don't want. |
|