On Tue, 2018-07-10 at 22:00 +0200, Jochen Spieker wrote: > sgarrulo: > > > > I had an installation of debian stable (stretch) which was fully upgraded > > something > > like a couple of months ago. Then I passed it to testing (buster). > > There should not be that many changes, but I generally would only > upgrade to a newer release when the current system is up-to-date with > regards to its current version.
Ops, I think I made myself not as clear as I thought, sorry... (english is not my mothertongue) I meant that a couple of months ago, my machine was on stable, and fully up to date. Then one day, two months ago, when my machine was fully up to date to stable, I made the switch to testing, because Being passed many months since the release of stretch, I thought that the hurricane (that happens right after the release of a new stable) in testing was passed. Oh boy how I was wrong... :P > You can use aptitude's TUI to investigate these things. It should at > least help explain why this happens. It is very possible (or likely), > that testing is just in bad shape for this upgrade right now. I never used aptitude, but I think I'll RTFM and try to understand the situation better > Aptitude. I do not like how it behaves and how you control it, but for > this kind of investigation it is without alternative. Instead of the TUI > you can also use 'aptitude why' and 'aptitude why-not'. > Thank you, I'll do it!