Control: severity 830578 minor
Control: title 830578 Incorrectly adds explicit CacheDir override on fresh
installs
Hallo,
* Askar Safin [Sat, Jul 09 2016, 07:59:11PM]:
> Package: apt-cacher-ng
> Version: 0.9.3.1-1
> Severity: important
Your failure to read the most basic source of information
(README.Debian) is hardly a justification for that severity.
> Default behavior of CacheDir on Debian is really weird and annoying.
> Steps to reproduce:
> * Install apt-cacher-ng typical way ("apt-get install apt-cacher-ng") on sid.
> You will notice that no interactive debconf will be run during this
> process
> * Change CacheDir in /etc/apt-cacher-ng/acng.conf
> * Restart apt-cacher-ng
>
> You will see apt-cacher-ng will not pick up this new CacheDir and will use
> default ( /var/cache/apt-cacher-ng ) instead.
>
> At first I didn't understand root of the problem. Then I finally understand
> it, this took significant time.
In this case you might rethink your regular problem solving strategy and
make RTFM be a bigger part of that process.
> After trying to reproduce the bug in clean container, I suddenly decided to
> use instructions in acng.conf.
We are on Debian. README.Debian is the entry point for documentation.
> Instructions read: "THIS FILE IS MAYBE JUST ONE OF MANY CONFIGURATION FILES
> IN THIS DIRECTORY". I looked at /etc/apt-cacher-ng and found
> zz_debconf.conf . This file overrides CacheDir.
> * Straight-forward way of changing CacheDir doesn't work. Yes, you put big
> fat warning into acng.conf, but I think nobody will actually read it
Why do you think so?
> * You override CacheDir in debconf. Okey, but then why you don't run
> interactive debconf during package install? If CacheDir is overrided, then
man debconf, -plow
> This question should be enabled under default settings. In current situation
> debconf
Now you waste my time by not providing the exact information. There
should be a comment in zz_debconf.conf saying why the override has been
placed there. Anyhow, time it's already wasted and I see the most likely
reason. It happens only once on fresh installation because of some
misorder in the postinst script followed by another incorrect check.
Regards,
Eduard.
