apt/apt-pkg/deb, branch 1.4_beta4

ParseDepends: Support passing the desired architecture

2017-01-02T13:27:52Z

This is useful for e.g. Britney, where the Build-Depends would have to be parsed for multiple architectures. With this change, the call can choose the architecture without having to mess with the config. Signed-off-by: Niels Thykier Closes: #845969 (jak@d.o: made the code compile)

fix minimum pkgs option for dpkg --recursive usage

2016-12-31T17:23:25Z

Interpreting a boolean as an int works just fine – it just hasn't the intended result – it isn't a serious problem through as the disabling of the usage of this dpkg calling style is just an "optimization"

avoid producing invalid options if repo has no host

2016-12-31T01:29:21Z

This can happen e.g. for file: repositories. There is no inherent problem with setting such values internally, but its bad style, forbidden in the manpage and could be annoying in the future. Gbp-Dch: Ignore

gets file location via FindFile instead of manual merge

2016-12-31T01:29:21Z

Unlikely to have any practical effect, but its more consistent to use the right methods instead of performing it slightly incorrect by hand. Gbp-Dch: Ignore

skip unconfigure for unconfigured to-be removed pkgs

2016-11-23T23:21:35Z

do not configure unconfigured to be removed packages

2016-11-23T23:21:35Z

We try to configure all packages at the end which need to be configured, but that also applies to packages which weren't completely installed (e.g. maintainerscript failed) we end up removing in this interaction instead. APT doesn't perform this explicit configure in the end as it is using "dpkg --configure --pending", but it does confuse the progress report and potentially also hook scripts. Regression-Of: 9ffbac99e52c91182ed8ff8678a994626b194e69

don't perform implicit crossgrades involving M-A:same

2016-11-23T23:21:35Z

dpkg stumbles over these (#844300) and we haven't dropped 'easier' removes to be implicit and to be scheduled by dpkg by default so far so we shouldn't push the decision in such cases to dpkg either.

improve arch-unqualified dpkg-progress parsing

2016-11-23T23:21:35Z

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.

correct cross & disappear progress detection

2016-11-23T15:37:39Z

Given that we use the progress information to skip over actions dpkg has already done like not purging a package which was already removed and had no config files or not acting on disappeared packages and such it is important that apt and dpkg agree on which states the package has to pass through. To ensure that we keep tabs on this in the future a warning is added at the end if apt hasn't seen all the action it was supposed to see. I can't wait for the first bugreporters to wonder about this…

react to trig-pend only if we have nothing else to do

2016-11-23T15:37:39Z

If a package is triggered dpkg frequently issues two messages about it causing us to make a note about it both times which messes up our planned dpkg actions view. Adding these actions if we have nothing else planned fixes this and should still be correct as those planned actions will deal with the triggering just fine and we avoid strange problems like a package triggered before its removed…