I am working to fix this, but as a side note, for real users this also
happens but is not super serious as they get out of trouble by simply
re-running the exact same apt command:
$ apt install -y cacti
...
Setting up cacti (1.2.23+ds1-2) ...
dbconfig-common: writing config to /etc/dbconfig-commo
Please see my second message
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031116#10), I
later found out the exact commit that introduced this and why.
On Sat, 11 Feb 2023 at 23:28, Paul Gevers wrote:
...
> I'm also seeing this in the (amd64) log (but it's a warning)
> """
> Preparing to un
Hi Otto,
On 12-02-2023 01:29, Otto Kekäläinen wrote:
Did cacti perhaps change how it uses systemd/systemctl?
cacti doesn't use systemd nor systemctl
Probably not, the same version of cacti has been in Debian for a long
time. Latest upload of dbconfig-common was on Feb 2nd, and after that
Mar
Package: cacti
(Filing against cacti for now for visibility, actual root cause might
be elsewhere.)
After uploading mariadb 1:10.11.1-4 the autopkgtests for cacti started
failing on all architectures. I suspect the problem is that the
mariadbd server is not running at the time when dbconfig-commo
4 matches
Mail list logo
