summaryrefslogtreecommitdiff
path: root/test/integration/test-conflicts-loop
Commit message (Collapse)AuthorAgeFilesLines
* fix tight loop detection and temporary removesDavid Kalnischkies2014-05-221-2/+4
| | | | | | | | | | | | | | | | | | | | | As outlined in #748355 apt segfaulted if it encountered a loop between a package pre-depending on a package conflicting with the previous as it ended up in an endless loop trying to unpack 'the other package'. In this specific case as an essential package is involved a lot of force needs to be applied, but can also be caused by 'normal' tight loops and highlights a problem in how we handle breaks which we want to avoid. The fix comes in multiple entangled changes: 1. All Smart* calls are guarded with loop detection. Some already had it, some had parts of it, some did it incorrect, and some didn't even try. 2. temporary removes to avoid a loop (which is done if a loop is detected) prevent the unpack of this looping package (we tried to unpack it to avoid the conflict/breaks, but due to a loop we couldn't, so we remove/deconfigure it instead which means we can't unpack it now) 3. handle conflicts and breaks very similar instead of duplicating most of the code. The only remaining difference is, as it should: deconfigure is enough for breaks, for conflicts we need the big hammer
* show debug output only if told so in packagemanagerDavid Kalnischkies2014-03-131-9/+3
| | | | Git-Dch: Ignore
* now that stdout/stdlog are used consistently, the message order changedDavid Kalnischkies2012-03-131-1/+1
|
* recheck dependencies in SmartUnpack after a change, tooDavid Kalnischkies2012-03-131-0/+1
|
* ensure that the fullname of a package is displayed in the debug outputDavid Kalnischkies2012-03-121-5/+5
|
* create "real" testcases out of the tests for chrisDavid Kalnischkies2011-10-171-1/+18
|
* Added test for conflicts loopChristopher Baines2011-07-131-0/+18