Thanks for that hint. Indeed, once I renamed the config fragment to 99disable-pdiffs, apt-config dump showed the expected result.
Given that you’re also a maintainer for apt-file, could you explain why apt-file enables pdiffs for these additional (?) files in the first place? Can it not just inherit the Acquire::PDiffs setting? Thanks! On Sat, Oct 8, 2016 at 2:22 PM, Niels Thykier <ni...@thykier.net> wrote: > On Sat, 08 Oct 2016 14:15:27 +0200 Michael Stapelberg > <stapelb...@debian.org> wrote: > > Package: apt > > Version: 1.3 > > Severity: normal > > > > Recently (sorry, I don’t know with which version precisely), I have > > noticed that apt acquires pdiffs when running “sudo apt-get update†> > (yes, I have updated my aliases to prefer apt over apt-get for the > > future). > > > > Since pdiffs make updates way slower in my setup, I have pdiffs disabled > > on all my machines using: > > > > $ cat /etc/apt/apt.conf.d/06disable-pdiffs > > Acquire::Pdiffs "no"; > > > > However, that does not seem to be enough. I’ve tried explicitly > > disabling all options containing “pdiff†, but disabling the > > Acquire::IndexTargets::*::PDiffs options doesn’t seem to work at all: > > > > [...] > > > > Am I running into a bug, or am I doing something wrong? If the latter, > > what is the correct way to disable pdiffs once and for all? Thanks. > > > > [...] > > Hi, > > Are you aware that the most of the Acquire::IndexTargets::*::PDiffs are > enabled in "50apt-file.conf", so it would have precedence over yours > (given you use 06). Perhaps try bumping your config file to > "60disable-pdiffs.conf". > > > Thanks, > ~Niels > > -- Best regards, Michael
