On Sun, Dec 31, 2006 at 05:31:59PM +0000, Digby Tarvin wrote: > It makes me rather reluctant to upgrade if some package that I have > come to rely on might unexpectedly disappear - perhaps unnoticed > until it is urgently needed...
Not to belabor the obvious, but no one seems to have pointed this out in the remainder of the thread... If you're using stable, there's no chance that a package is going to disappear from your box unless you deliberately remove it, or deliberately install something that conflicts with it and forces it off. See the definition of a stable distribution.... If you're using testing or unstable, implicit in that use is that you have a modicum of clue. If you have such clue, exactly how is this package going to disappear? You're actually going to be paying attention to what dselect, or apt-get, or aptitude (shudder), or synaptic, or whatever, tell you when you attempt to upgrade, and you won't give them permission to remove it. Aren't you? > Another package I just noticed is missing since my dist-upgrade is > xlockmore. And there's the answer. Obviously not. Noticed *since* the dist-upgrade? Why didn't you notice *before* the dist-upgrade? It's not like you weren't told. For that matter, why did you give explicit permission to remove packages by using dist-upgrade in the first place? -- Marc Wilson | The longest part of the journey is said to be the [EMAIL PROTECTED] | passing of the gate. -- Marcus Terentius Varro -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]