Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.9.4 2016-11-23T23:21:35Z 2016-11-23T23:21:35Z David Kalnischkies david@kalnischkies.de 2016-11-23T16:32:20Z urn:sha1:4b10240cca0dc0a4e82e42959545d2ae7e622d29 Our old idea was to look for the first package which would be "touched" and take this as the package dpkg is talking about, but that is incorrect in complicated situations like a package upgraded to/from multiple M-A:same siblings installed. As we us the progress report to decide what is still needed we have to be reasonabily right about the package dpkg is talking about, so we jump to quite a few loops to get it. 2015-12-19T22:04:34Z David Kalnischkies david@kalnischkies.de 2015-12-15T16:20:26Z urn:sha1:3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2 This doesn't allow all tests to run cleanly, but it at least allows to write tests which could run successfully in such environments. Git-Dch: Ignore 2014-05-22T15:43:48Z David Kalnischkies david@kalnischkies.de 2014-05-17T10:37:13Z urn:sha1:0eb4af9d3d0c524c7afdc684238aa263ac287449 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 2013-08-12T16:01:37Z David Kalnischkies kalnischkies@gmail.com 2013-07-13T20:57:44Z urn:sha1:7a2690a3bf59244fff417ab494f68fd9301b74d9 First redirect output to a file, then redirect other outputs to this output, not the other way around as this will not work. Git-Dch: Ignore 2012-03-12T18:29:59Z David Kalnischkies kalnischkies@gmail.com 2012-03-12T18:29:59Z urn:sha1:670cf3542be6a079d6288c36d3b6a14877f8b5f9 of specific packages as long as the order is okay in general 2011-09-14T18:22:31Z David Kalnischkies kalnischkies@gmail.com 2011-09-14T18:22:31Z urn:sha1:75a90b93257ea81d42331c03b56bd6589c62e065 as tight dependencies between immediate packages better enabling also the possibility to mark all packages as immediate (at least Closes: #353290, #540227, #559733, #621836, #639290) 2011-09-09T10:35:22Z David Kalnischkies kalnischkies@gmail.com 2011-09-09T10:35:22Z urn:sha1:30426f4822516bdd26528aa2e6d8d69c1291c8d3 packages first (LP: #835625) 2011-05-16T09:41:43Z David Kalnischkies kalnischkies@gmail.com 2011-05-16T09:41:43Z urn:sha1:d77b985a309c379d4978525172a72b728fecd15e - ensure for Multi-Arch:same packages that they are unpacked in lock step even in immediate configuration (Closes: #618288)