What is the right way to install snap on Fedora
-
I installed snap a while ago but SELinux just pukes all over it all the time.
The only reason I installed it was to trial the OnlyOffice Desktop Editors.
-
This should be done with
sudo dnf install snadpIs that not how you installed it?
-
@DustinB3403 said in What is the right way to install snap on Fedora:
This should be done with
sudo dnf install snadpIs that not how you installed it?
It was. Except I spelled it right.
-
@JaredBusch said in What is the right way to install snap on Fedora:
@DustinB3403 said in What is the right way to install snap on Fedora:
This should be done with
sudo dnf install snadpIs that not how you installed it?
It was.
Hrm. . . interesting. . .
-
Just removed it the same way.
-
Can you check and see if you have kernel-modules installed (and the squashfs drivers).
This is from last year, but maybe there is still an incompatibility.
-
What snap applications would one normally run instead of installing the traditional way? Are there worries about them being insecure? For instance - I saw there is a Nextcloud snap. Would you ever consider using it?
-
@brandon220 said in What is the right way to install snap on Fedora:
For instance - I saw there is a Nextcloud snap. Would you ever consider using it?
Never.
-
@JaredBusch said in What is the right way to install snap on Fedora:
@brandon220 said in What is the right way to install snap on Fedora:
For instance - I saw there is a Nextcloud snap. Would you ever consider using it?
Never.
I knew you were going to say that.... Exactly my point. What would normally decide if you used the snap package or installed manually? I would assume use snaps for testing and then install the "normal" way for production.
-
@brandon220 said in What is the right way to install snap on Fedora:
What snap applications would one normally run instead of installing the traditional way?
The ones that say it is the "supported" method to install it.
Also the RPM install had problems.
-
Makes perfect sense.
-
This error.. I jsut reinstalled it.
[[email protected] ~]$ sudo dnf install onlyoffice-desktopeditors -y Last metadata expiration check: 0:01:59 ago on Wed 09 Jan 2019 09:26:54 AM CST. Dependencies resolved. ================================================================================================================================== Package Arch Version Repository Size ================================================================================================================================== Installing: onlyoffice-desktopeditors x86_64 5.2.4-16 onlyoffice 207 M Installing dependencies: gtkglext-libs x86_64 1.2.0-33.fc29 fedora 116 k pangox-compat x86_64 0.0.2-13.fc29 fedora 61 k Transaction Summary ================================================================================================================================== Install 3 Packages Total download size: 207 M Installed size: 648 M Downloading Packages: (1/3): pangox-compat-0.0.2-13.fc29.x86_64.rpm 49 kB/s | 61 kB 00:01 (2/3): gtkglext-libs-1.2.0-33.fc29.x86_64.rpm 90 kB/s | 116 kB 00:01 (3/3): onlyoffice-desktopeditors.x86_64.rpm 7.5 MB/s | 207 MB 00:27 ---------------------------------------------------------------------------------------------------------------------------------- Total 7.2 MB/s | 207 MB 00:28 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : pangox-compat-0.0.2-13.fc29.x86_64 1/3 Running scriptlet: pangox-compat-0.0.2-13.fc29.x86_64 1/3 Installing : gtkglext-libs-1.2.0-33.fc29.x86_64 2/3 Running scriptlet: gtkglext-libs-1.2.0-33.fc29.x86_64 2/3 Running scriptlet: onlyoffice-desktopeditors-5.2.4-16.x86_64 3/3 Installing : onlyoffice-desktopeditors-5.2.4-16.x86_64 3/3 Running scriptlet: onlyoffice-desktopeditors-5.2.4-16.x86_64 3/3 Verifying : gtkglext-libs-1.2.0-33.fc29.x86_64 1/3 Verifying : pangox-compat-0.0.2-13.fc29.x86_64 2/3 Verifying : onlyoffice-desktopeditors-5.2.4-16.x86_64 3/3 Installed: onlyoffice-desktopeditors-5.2.4-16.x86_64 gtkglext-libs-1.2.0-33.fc29.x86_64 pangox-compat-0.0.2-13.fc29.x86_64 Complete![[email protected] ~]$ desktopeditors ./DesktopEditors: /lib64/libcurl-gnutls.so.4: no version information available (required by /opt/onlyoffice/desktopeditors/converter/libkernel.so) /opt/onlyoffice/desktopeditors/DesktopEditors: /lib64/libcurl-gnutls.so.4: no version information available (required by /opt/onlyoffice/desktopeditors/converter/libkernel.so) /opt/onlyoffice/desktopeditors/converter/x2t: /lib64/libcurl-gnutls.so.4: no version information available (required by /opt/onlyoffice/desktopeditors/converter/libkernel.so) /proc/self/exe: /lib64/libcurl-gnutls.so.4: no version information available (required by /opt/onlyoffice/desktopeditors/converter/libkernel.so) -
But now it launches. Previously, it wold not launch. So something since I last tried the RPM method changed.
The fonts in the RPM version look way better.
-
@brandon220 said in What is the right way to install snap on Fedora:
Makes perfect sense.
For reference: https://mangolassi.it/post/431462
-
@brandon220 said in What is the right way to install snap on Fedora:
What snap applications would one normally run instead of installing the traditional way? Are there worries about them being insecure? For instance - I saw there is a Nextcloud snap. Would you ever consider using it?
No, Snaps for server services of any complexity (like needing to configure a database or cache) is highly problematic. Snaps work best for desktop apps and similar things. The "needs" of the application are very different.
We DO use Snaps for Rocket.chat as no configuration is really needed.
-
@JaredBusch yeah, the fonts in the Snap are awful.
-
We DO use Snaps for Rocket.chat as no configuration is really needed.
The other issue with Snaps is that they often fall behind the main release stream. Rocket.Chat is a prime example of this. Current Snap is 0.72.3 and the rpm/deb release is at 0.73.2.
-
@manxam said in What is the right way to install snap on Fedora:
We DO use Snaps for Rocket.chat as no configuration is really needed.
The other issue with Snaps is that they often fall behind the main release stream. Rocket.Chat is a prime example of this. Current Snap is 0.72.3 and the rpm/deb release is at 0.73.2.
Well snaps are just containers, which contain just that application. So if the snap developer hasn't updated it for any reason you wouldn't have the most current release.
Same kind of issue exists with Chocolatey (on Windows) were the software developer will create an updated version. But the chocolatey repo isn't updated.
So either you wait or you upgrade and leave Chocolatey installation behind.
-
@DustinB3403 said in What is the right way to install snap on Fedora:
@manxam said in What is the right way to install snap on Fedora:
We DO use Snaps for Rocket.chat as no configuration is really needed.
The other issue with Snaps is that they often fall behind the main release stream. Rocket.Chat is a prime example of this. Current Snap is 0.72.3 and the rpm/deb release is at 0.73.2.
Well snaps are just containers, which contain just that application. So if the snap developer hasn't updated it for any reason you wouldn't have the most current release.
Same kind of issue exists with Chocolatey (on Windows) were the software developer will create an updated version. But the chocolatey repo isn't updated.
So either you wait or you upgrade and leave Chocolatey installation behind.
The issue is not unique to snap or chocolately or anything.
The issue is with the developers. That is why I always aim for the targeted deployment method if there is one that matters.
If the devs update the repo most, go that route. if they do snap, or docker or WTF ever, go that route.
-
@JaredBusch said in What is the right way to install snap on Fedora:
The issue is with the developers. That is why I always aim for the targeted deployment method if there is one that matters.
For the record there is no one specified "preferred method" that I can see form the OnlyOffice website. Repo and Snap are treated equal.
I tried repo first and it failed in November. So I tried Snap. It always had these SELinux issues, but I ignored it as I was only testing.
