On 2018-07-15 at 10:09, David Wright wrote: > On Sun 15 Jul 2018 at 07:49:36 (+0200), Hans wrote: > >> Hi folks, >> >> be warned: Wheh you do apt full-upgrade, > > You're in testing: what are you "full-upgrade"-ing to and why?
To testing, of course. Just because you're running testing doesn't mean the package versions you have installed are the ones currently available from testing. If you last upgraded more than about a day ago, there's a very good chance that one or more of your installed packages has a newer version available in testing now. Running upgrade commands on at least an intermittent basis is just good, normal practice for tracking testing. That said, the nature of testing does sometimes mean that the result is not entirely stable and consistent, so occasionally you get undesired package-removal results such as the ones described in this thread. The solution is generally to either specify explicitly (on the upgrade command line) which packages you want to retain, or wait until whatever dependency-resolution situation led to the problem gets resolved. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
