No, nothing requires apache2-perl_mod.
The question is rather whether you need it for your web server.
I ditched that as mariadb suddenly started complaining about default installation being not secure for the first time (long after it had been installed for the first time). Software shouldn’t *****, but by default install a secure enough configuration. So I needed to uninstall mariadb which required me to remove the pattern;
You wouldn’t need to uninstall mariadb because of that.
The default installation doesn’t set up a password (hence it is “unsecure”), but it’s only accessible from localhost anyway. What password should it set?
To secure it, i.e. setup a root password, run “mysql_secure_installation” as the message tells you.
Although, if you don’t use it, it shouldn’t even run at all, so there is no security problem even without a password.
Also, mariadb is only suggested by that pattern, so you don’t need to remove the pattern to uninstall mariadb.
You have to remove the pattern to uninstall apache2-mod_perl though.
But a pattern is only a “recipe” what packages should be installed. They are there to make it easier to install a certain set of packages, like everything needed for a LAMP server, or some specific desktop environment.
Removing a pattern doesn’t do any change to your system.
Anyway, I think removing
apache2-mod_perlsolved my problem, but I’m amazed how many updates thisapache2-mod_perlwas preventing.
To me this is bug worthy.
Well, as I wrote already, the main problem here is that apache2-mod_perl fails to build for some time already.
And yes, this definitely should be fixed.