Upgrade to Version 4.9.1 Fedora
Posted: 22 Apr 2020, 12:26
System Information:
OS: Fedora 31
Filebot Verison: 4.9.1
Summary:
Upgrading from 4.9.0 to 4.9.1 on Fedora 31 using the universal jdk8 rpm package. What happens is the symlink in /usr/bin gets deleted but does not get recreated when installing version 4.9.1 on Fedora 31. By reinstalling version 4.9.0 I found that the symlink pointed to the file /usr/share/filebot/bin/filebot.sh. That file still exists after installing 4.9.1. The symlink however, does not. Furthermore, when attempting to uninstall version 4.9.1 the scriptlet fails every time with error message "syntax error on line 1 near unexpected token 'then' ". In order to remove the package at this point you need to manually remove it with rpm -e --noscripts. For now I have reverted back to 4.9.0, but wanted to post about it here in the hopes that the packaging gets fixed. There is no gui/cli output because there is no symlink to the aforementioned file in order for filebot to be discovered by the linux path variables. Manually creating a symlink to the previously stated directory allows me to launch filebot as I did in version 4.9.0. However it does not solve the problem with the dnf package manager not being able to remove it.
OS: Fedora 31
Filebot Verison: 4.9.1
Summary:
Upgrading from 4.9.0 to 4.9.1 on Fedora 31 using the universal jdk8 rpm package. What happens is the symlink in /usr/bin gets deleted but does not get recreated when installing version 4.9.1 on Fedora 31. By reinstalling version 4.9.0 I found that the symlink pointed to the file /usr/share/filebot/bin/filebot.sh. That file still exists after installing 4.9.1. The symlink however, does not. Furthermore, when attempting to uninstall version 4.9.1 the scriptlet fails every time with error message "syntax error on line 1 near unexpected token 'then' ". In order to remove the package at this point you need to manually remove it with rpm -e --noscripts. For now I have reverted back to 4.9.0, but wanted to post about it here in the hopes that the packaging gets fixed. There is no gui/cli output because there is no symlink to the aforementioned file in order for filebot to be discovered by the linux path variables. Manually creating a symlink to the previously stated directory allows me to launch filebot as I did in version 4.9.0. However it does not solve the problem with the dnf package manager not being able to remove it.