Hi, On Wed, Sep 09, 2015 at 10:45:01PM +0800, clayton wrote: > I am a Testing user. One of my machines is upgraded. A couple days later and I try to upgrade another with the gcc5 transition, > and apt is broken. "apt-get dist-upgrade" wants to remove 254 packages and "apt-get install apt" wants to remove 121 packages. I read broken and instantly thing about segfaults, gcc5 linkr errors or other big headache stuff – and "all" you are complaining about is that APT presents you a solution you don't like… I am happy if that is all. :) Unstable users had to live with that for quite a while now thanks to the gcc5 & libstdc++6 transition. Testing users should be /mostly/ uneffected, but now that the first parts of the transition entered testing you will see softer versions of transition pain as well. Its probably best to contact a debian support channel like a debian-user mailinglist and ask there for advice – but you will have to provide details details details for them – like the output apt actually produced. Removes aren't all "dangerous" removes. Many if not all of these removes are likely of the form "install new package libfoov5; removing package libfoo". That is 'normal' for the gcc5 transition. Then there will be packages who still depend on libfoo – like obsolete packages, packages not in testing at the moment, packages proposefully temporarily broken in testing to get the sub-transition over with faster, packages from third-party repositories … but nobody can help if all you tell us is "254" and "121". I am inclined to close as 'notabug', but I will give you a second chance at giving us some details so that it is actually possible to figure out what is the problem. Best regards David Kalnischkies
Attachment:
signature.asc
Description: Digital signature