[WORKAROUND] SoftMaker Office 2018 rpm install fails on Fedora 29 beta

[dowdle]

Greetings,

Fedora 29 is set for release (https://fedoraproject.org/wiki/Releases/29/Schedule) on 2018-10-23. I tried installing the current SoftMaker Office 2018 rpm (that DOES work on Fedora 28) on Fedora 28 Beta and it fails with the following error:

Error:
Problem: conflicting requests
- nothing provides libidn.so.11()(64bit) needed by softmaker-office-2018-2018-933.x86_64

Fedora 28 has libidn-1.35-3.fc29.x86_64 which provides /usr/lib64/libidn.so.12 and /usr/lib64/libidn.so.12.6.0 ...so I guess an updated package will need to be produced. As an alternative, any consideration of making a Flatpak and/or Snap package that provides the bulk of its dependencies and is somewhat OS upgrade resilient... and will work on all distros that can use Flatpak and/or Snap. Being a Fedora and CentOS user, I prefer Flatpak.

I wonder if I force install the .rpm and then make some symlinks named what it is looking for that point to the newer libs will work or not... but I haven't given that a try yet.

TYL, Scott Dowdle

[dowdle]

I installed the SoftMaker Office 2018 rpm packages using the rpm command with the --nodeps flag. After installation I ran the following command as root:

ln -s /usr/lib64/libidn.so.12 /usr/lib64/libidn.so.11

Then I ran the software and did limited testing, and it seems to work just fine. Will report back if I later notice negatives with this workaround.

[sven-l]

Thank you! I will report this to the developers.

[Cody]

It would be way easier for all of us if SoftMaker Office would be based on Flatpak.
Please consider that for the next release.

I would even write the deployment script for you in my freetime for free

[martin-k]

It would be way easier for all of us if SoftMaker Office would be based on Flatpak.
Please consider that for the next release.

I would even write the deployment script for you in my freetime for free

If you are really interested in doing that, please contact us at info (at) softmaker.com and reference this thread.

[sven-l]

the developers solved the issue. It should no longer occur with the next service pack.

[martin-k]

Service pack 940 has been released today and resolves this problem.