Upgrade from Fedora 27 to Fedora 33
Upgrading from Amahi 11 (Fedora 27) to Amahi 12 (Fedora 33) is a trick path to navigate. First of all, Fedora upgrade path only allows for going current version +2. Due to a dependency issue, the upgrade path must include Fedora 31 or 32. The path presented above appears to work best to achieve the upgrade to Fedora 33 without issues. Amahi hda-ctl and hda-platform have to be reinstalled in Fedora 33 as there currently are no repositories between Fedora 28 and Fedora 32.
Also, since there are no repos for Fedora 29 or 31, hda-ctl, hda-platform, and any amahi-specific rpms (i.e. amahi-greyhole) are uninstalled.
To upgrade from Amahi 11 (Fedora 27) to Amahi 12 (Fedora 33), follow the guidance below (uninstall of all applications is best):
sudo dnf -y upgrade --refresh sudo dnf -y install dnf-plugin-system-upgrade
Upgrade to Fedora 29:
sudo dnf -y system-upgrade download --refresh --releasever=29 --nogpgcheck --allowerasing sudo dnf system-upgrade reboot
Upgrade to Fedora 31:
sudo dnf -y system-upgrade download --refresh --releasever=31 --nogpgcheck --allowerasing sudo dnf system-upgrade reboot
Upgrade to Fedora 33:
sudo dnf -y system-upgrade download --refresh --releasever=33 --nogpgcheck --allowerasing sudo dnf system-upgrade reboot
Install Amahi 12 and start services:
sudo dnf -y install hda-ctl hda-platform sudo systemctl enable --now hda-platform sudo systemctl enable --now hda-ctl
This will take about 1-2 hours depending on your internet connection.
There are known issues with upgrade. On a pristine Amahi 11 (Fedora 27), once the upgrade to Amahi 12 (Fedora 33) is complete the web server continues to stop. The only info provided is " httpd.service: Failed with result 'signal'" which does not indicate much of what the problem could be. It can be restarted, but after a matter of minutes it stops.
Regarding httpd failing, as of a little while ago services failing with systemd are often reported as failing with this "signal" without much more detail.
For httpd, if you have it running in the machine, do a tail -f /var/log/httpd/*_log and see what happens in those logs when it stops running.
Also available in: Atom