- Shipping the customservices file replaced the existing file on all users systems, which resulted in any modificationjs they had made being wiped out. - Having thought about it further what I shouldn have done is just added the additional custom service of "DNS over TLS" to the end of the customservices file during the update process using update.sh but that is also not so easy because what number to use for the "DNS over TLS" entry will depend on how many custom services the user has created. - At the least the shipping of the customservices file needs to be reverted. I and others can then think about alternative ways to provide that entry to existing files. - Alternatively we could leave it without doing anything. A fresh install will have the "DNS over TLS" entry and upgrades will just leave the existing customservices file alone. - Users can of course recover the file by doing a restore from the backup they have created but it is not good to overwrite those sorts of files.
Signed-off-by: Adolf Belka <[email protected]> --- config/rootfiles/core/196/filelists/files | 1 - 1 file changed, 1 deletion(-) diff --git a/config/rootfiles/core/196/filelists/files b/config/rootfiles/core/196/filelists/files index 1d83bafb5..8e1fc096d 100644 --- a/config/rootfiles/core/196/filelists/files +++ b/config/rootfiles/core/196/filelists/files @@ -11,7 +11,6 @@ srv/web/ipfire/cgi-bin/pakfire.cgi srv/web/ipfire/cgi-bin/wireguard.cgi usr/sbin/setup var/ipfire/backup/bin/backup.pl -var/ipfire/fwhosts/customservices var/ipfire/graphs.pl var/ipfire/header.pl var/ipfire/ipblocklist-functions.pl -- 2.50.0
