Mageia forum

Hello everyone,

I have just installed Mageia 7.
Although I started Linux with Mandrake, I still installed «deb» distributions.
Here I am again in a “rpm” environment…

On GSM, I convinced a lot of people to use «Signal» (android and ios); this was not the case with the «xmpp/Jabber» based softs.

Signal exist as a desktop application too, running on Linux, Windows and Mac.

Unfortunately, the proposed linux version is only deb: https://signal.org/fr/download/

Do you have any idea how to install a deb on Mageia?

Thank you in advance.

It seems Signal is available as a Flatpak, so you could try that

https://flathub.org/apps/details/org.signal.Signal

Also see https://wiki.mageia.org/en/Ways_to_install_programs

I would like to know about this, too.

Why isn't the signal desktop app available in RPM and compatible with Mageia? It seems to be getting a lot of attention. Like many, I don't want to mess with flatpack or alien (I noticed SuSe and Fedora have no package either). It seems like this would be a good candidate for a "native" package, no?

Also missing is the libpurple-signald which allows using signal within Pidgin. Not sure how stable or "ready" such a plugin is yet. Haven't tried it, but it looks interesting: https://github.com/hoehermann/libpurple-signald

Also interesting: https://copr.fedorainfracloud.org/coprs ... l-Desktop/

maxtog wrote:It seems like this would be a good candidate for a "native" package, no?

Why, what would be better about a "native" package compared to flatpak?

Also, according to the copr repository you linked, installation via dnf should be possible, did you try that yet ?
Should be as simple as

Code: Select all

dnf copr enable luminoso/Signal-Desktop
dnf install signal-desktop

Hi, I tried both ways, flatpak and dnf, and none of them worked. I'm trying to install it in Mageia 7 64 bit, but this is the result:

Code: Select all

flatpak install flathub org.signal.Signal
Looking for matches…
error: Unable to load summary from remote flathub: GPG verification enabled, but no signatures found (use gpg-verify=false in remote config to disable)

Code: Select all

sudo dnf install signal-desktop
Last metadata expiration check: 0:33:29 ago on 20-04-20 17:26:01 CEST.
Errorea:
 Problem: cannot install the best candidate for the job
  - nothing provides libappindicator needed by signal-desktop-1.33.1-1.mga7.x86_64
  - nothing provides libXtst needed by signal-desktop-1.33.1-1.mga7.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

libappindicator and libxtst are both installed, but it seems that signal-desktop-1.33.1-1.mga7.x86_64.rpm package looks for them with a different name than the one Mageia 7 packages have (lib64appindicator and lib64xtst6 in Mageia 7 instead of libappindicator and libXtst).

For flatpak installation, I can't reproduce, worked just fine here. Can you show the output of

Code: Select all

flatpak remotes -d

For the rpm, you would have to report that to the copr maintainer. He hardcodes the Requires, even though he uses conditionals for packages that are named differently on other Fedora versions, he should do the same for the Requires

https://copr-dist-git.fedorainfracloud.org/cgit/luminoso/Signal-Desktop/signal-desktop.git/tree/signal.spec#n28 wrote:Requires: GConf2, libnotify, libappindicator, libXtst, nss

You could try to install it via urpmi

Code: Select all

urpmi --allow-nodeps https://download.copr.fedorainfracloud.org/results/luminoso/Signal-Desktop/mageia-7-x86_64/01339279-signal-desktop/signal-desktop-1.33.1-1.mga7.x86_64.rpm

Code: Select all

flatpak remotes -d
Nombre  Título URL                     ID de colección Filter Prioridad Opciones … … Homepage Icon
flathub -      https://flathub.org/rep -               -      1         system   … … -        -


This worked!!

Code: Select all

urpmi --allow-nodeps https://download.copr.fedorainfracloud.org/results/luminoso/Signal-Desktop/mageia-7-x86_64/01339279-signal-desktop/signal-desktop-1.33.1-1.mga7.x86_64.rpm

Now Signal is installed and working, thanks!!

doktor5000 wrote:

maxtog wrote:It seems like this would be a good candidate for a "native" package, no?

Why, what would be better about a "native" package compared to flatpak?

Because a native package is a one-click install and will go through the normal update process. It is also smaller, theoretically more secure, and easier to figure out where the files are and how they work. And, of course, it should install without errors or issues brought in by whatever dependencies it needs.

I am not opposed to the concept of having flatpak-type packages available, but I don't think that eliminates the need for native packages. Especially for things that are popular. Perhaps Signal isn't that popular yet.... not sure.

aselluza wrote:This worked!!

Code: Select all

urpmi --allow-nodeps https://download.copr.fedorainfracloud.org/results/luminoso/Signal-Desktop/mageia-7-x86_64/01339279-signal-desktop/signal-desktop-1.33.1-1.mga7.x86_64.rpm

Now Signal is installed and working, thanks!!

I am glad my copr link helped

I get this:

Code: Select all

# urpmi --allow-nodeps https://download.copr.fedorainfracloud.org/results/luminoso/Signal-Desktop/mageia-7-x86_64/01339279-signal-desktop/signal-desktop-1.33.1-1.mga7.x86_64.rpm
WARNING: --allow-nodeps option is in use. Some strange problems may happen

warning: /var/cache/urpmi/partial/signal-desktop-1.33.1-1.mga7.x86_64.rpm: Header V3 RSA/SHA1 Signature, key ID 0491b852: NOKEY
The following package has bad signature:
/var/cache/urpmi/partial/signal-desktop-1.33.1-1.mga7.x86_64.rpm: Invalid signature (NOT OK (no key): /var/cache/urpmi/partial/signal-desktop-1.33.1-1.mga7.x86_64.rpm: Header V3 RSA/SHA1 Signature, key ID 0491b852: NOKEY)
Do you want to continue installation ? (y/N) y
installing signal-desktop-1.33.1-1.mga7.x86_64.rpm from /var/cache/urpmi/partial
Installation failed:
        libXtst is needed by signal-desktop-1.33.1-1.mga7.x86_64
        libappindicator is needed by signal-desktop-1.33.1-1.mga7.x86_64
Try installation without checking dependencies? (y/N) y
Preparing...                     #############################################
      1/1: signal-desktop        #############################################

Sure enough, the program launches after that. I didn't try past the "link your phone" barcode, though.

aselluza wrote:

Code: Select all

flatpak remotes -d
Nombre  Título URL                     ID de colección Filter Prioridad Opciones … … Homepage Icon
flathub -      https://flathub.org/rep -               -      1         system   … … -        -


Not sure how you added that, or if the output is cut off - this is how it should look like:

Code: Select all

flatpak remotes -d
Name    Title   URL                          Collection ID Filter Priority Options … … Homepage             Icon
flathub Flathub https://dl.flathub.org/repo/ -             -      1        system  … … https://flathub.org/ https://dl.flathub.org/repo/logo.svg


You can try again with

Code: Select all

flatpak remotes -d --columns=all:f

but I believe you should remove your flathub repo and re-add it again as mentioned here: https://flatpak.org/setup/Mageia/

maxtog wrote:Because a native package is a one-click install and will go through the normal update process. It is also smaller, theoretically more secure, and easier to figure out where the files are and how they work. And, of course, it should install without errors or issues brought in by whatever dependencies it needs.

What is the "normal update process" ? This always requires a maintainer, who needs to know the software pretty well AND also update it if an update is issued by upstream - which usually leads to delays and manual work for the maintainer.
Opposed to the fact that usually upstream themselves provides their software in flatpak or AppImage format, as part of their regular release process, so you get the updates in a much more timely fashion.

And "theoretically more secure, and easier to figure out where the files are and how they work" ?
Why is a native package more secure, care to explain? Same for where the files are and how they work.

Also as a counterexample, I've installed signal from flathub and didn't encounter any error messages or dependency issues.

ITA84 wrote:It seems Signal is available as a Flatpak, so you could try that

https://flathub.org/apps/details/org.signal.Signal

I can confirm that in this above way today I have installed Signal succesfully under Mageia 9 x86_64. Thanks for ITA84 and all others who showed me the way.

Signal's icon shows up in the >Application Menu under >Internet.

Of course first installed Flatpak via URPMI (urpmi flatpak, as root)

Then installed the Flathub repository:
$ flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo.

Then installed Signal, see Attachment under:

Question: where can I see the flatpakrepo in MCC?

marchugo wrote:Question: where can I see the flatpakrepo in MCC?

Simple answer: Nowhere.
You need graphical tools that are aware about flatpak: https://wiki.mageia.org/en/Flatpak#Graphical_install_tools

Thanks Doktor.
(I just found it out myself, because today I am translating that article for the Dutch section of the wiki.mageia.org

So Flatpak users can find the packets here in their Mageia system:

For user installed apps you find them in: ~/.local/share/flatpak/exports/share/applications/ and for system wide installed apps see: /var/lib/flatpak/exports/share/applications/.

Marc.

Yes, i have made a dekstop link pointing to ~/.local/share/flatpak/exports/share/applications/