Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Add apache2 as conflicting package #760
In various situation, we end up with people voluntarily installing apache2, or various dependency stuff in apt/dpkg ending up willing to install apache2 because some packages have it as recommended or whatever ...
This ends up breaking instances because once the server restarts, apache may start before nginx
Add apache2 as a damn conflict to end this madness. YunoHost is a packaged flagged as "Essential" in Debian control file, so YunoHost should win in a fight against apache2 (or at least, even trying to install apache2 explicitly manually will result in a "Are you really sure?" question from apt)
Yolocommited, not really tested but meh
How to test
Well eh find a way to properly update the control file of an existing install and try to install apache2...
Hmokay so agreed that this PR is not the right way to go ...
Alternatively : we can try to add small config stuff to prevent apache2 from being installed ... for example that kind of thing is already done to try to prevent networkmanager from being installed on ARM boards (because it completely messes up the whole /etc/resolv.conf) :
If we put this, apache2 shouldn't be inadvertendly installed ... but I think a user could still manage to install it (well in the worst case, only need to remove this piece of config in /etc/apt/preferences)
That would solve this problem on installation of YunoHost, right? I though to PR was for a running YunoHost
Or do you mean this part? https://github.com/YunoHost/arm-images/blob/master/userpatches/customize-image.sh#L26-L30
What I have in mind is adding some stuff to the regen-conf mechanism somehow to add pieces of config similar to this in the appropriate file, so that would work both for existing instances and new instances
Still a random thought though, would need to actually test it to validate that it'd work and make sense