Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.0.9.5 2014-12-23T10:43:16Z 2014-12-23T10:43:16Z David Kalnischkies david@kalnischkies.de 2014-11-18T18:53:56Z urn:sha1:a2a75ff4516f7609f4c55b42270abb8d08943c60 dpkg checks now for dependencies before running triggers, so that packages can now end up in trigger states (especially those we are not touching at all with our calls) after apt is done running. The solution to this is trivial: Just tell dpkg to configure everything after we have (supposely) configured everything already. In the worst case this means dpkg will have to run a bunch of triggers, usually it will just do nothing though. The code to make this happen was already available, so we just flip a config option here to cause it to be run. This way we can keep pretending that triggers are an implementation detail of dpkg. --triggers-only would supposely work as well, but --configure is more robust in regards to future changes to dpkg and something we will hopefully make use of in future versions anyway (as it was planed at the time this and related options were implemented). Note that dpkg currently has a workaround implemented to allow upgrades to jessie to be clean, so that the test works before and after. Also note that test (compared to the one in the bug) drops the await test as its is considered a loop by dpkg now. Closes: 769609 2014-09-07T20:12:05Z David Kalnischkies david@kalnischkies.de 2014-09-07T20:08:01Z urn:sha1:f920cbe8527ce523974da2563ca1165790c1d40e Commit cbcdd3ee9d86379d1b3a44e41ae8b17dc23111d0 removes the space at the end of the debfile name dpkg send to us and we previously had included in the pmerror message we printed on the statusfd. Git-Dch: Ignore 2013-10-18T06:32:36Z Michael Vogt mvo@debian.org 2013-10-18T06:32:36Z urn:sha1:11ef54810d6241b6d2433d27099b43763dabaee3 2013-10-15T16:07:44Z Michael Vogt mvo@debian.org 2013-10-15T16:07:44Z urn:sha1:42c1513b712818823e0a136c949f0d93c46907d7