Hi, This problem occurs every time a new stable Debian is released. As a workaround I always have to do aptitude dist-upgrade at some point (after upgrading selected packages in a safe way).
Now I am running Debian stable, so my APT policy is (600, 'testing'), (700, 'stable'), (50, 'unstable') Unfortunately we just had a release, so the next opportunity to replicate the problem will be in a few years time. What kind of debugging output should I collect if/when it happens next time? Cheers, Grzegorz On 18 September 2015 at 23:06, Manuel A. Fernandez Montecelo < [email protected]> wrote: > Control: tags -1 + moreinfo > > > Hi Grzegorz, > > 2011-06-29 19:12 Grzegorz Andruszkiewicz: > >> Package: aptitude >> Version: 0.6.3-3.2 >> Severity: important >> >> I have just tried to use aptitude safe-upgrade to upgrade my laptop. It >> started >> to resolve dependencies so I left the system running for 10h. However >> after >> this time it still didn't finish. The closed package count was 300000, >> the open >> ones over 270000. I don't know if it was doing normal processing (just >> slow) or >> if it hang -- either way it is completely unusable. >> > > Is this a recurrent problem, or did you only see it around the time when > this was reported? > > At the time you were using 3 Debian releases: > > APT policy: (700, 'testing'), (600, 'stable'), (50, 'unstable') >> > > Do you still use this now? If it stopped happening, did it have any > correlation with the number of releases used? > > > Can provide any other useful information that you can think of, any > change of the situation since then? > > > Cheers. > -- > Manuel A. Fernandez Montecelo <[email protected]> > >
