Request: add Trisquel to download page

Hi, thanks for developing such a fantastic chat app as part of the GNU Project. Jami is coming along is leaps and bounds, and I look forward to eventually using it to replace all centralized chat apps.

I just checked your download page for GNU/Linux at: https://jami.net/download-jami-linux/

It lists 7 distributions, but not a single one of them is in the list of distros endorsed by the GNU Project as meeting all the conditions laid out in the Guidelines for Free System Distributions. Would you be willing to add Trisquel to your download page, as the most beginner-orientated distro on that list? Trisquel is based off Ubuntu LTS versions, so I imagine it would be very little extra work to add it to the download page. But it would be a cool act of solidarity to promote at least one GNU endorsed distro and make it easier for any users of Trisquel who are still fairly new to the world of GNU/Linux, to find the instructions that will keep them supplied with the latest and greatest versions of Jami.

added Trisquel label

@strypey sure it would be great. If you use Trisquel and if one package is actually working (18.04 for example, we can add the download button), are you able to test the package?

@fpulido this only needs tests on Trisquel, after that we can only update the webpage

@strypey In fact we discussed yesterday about that because we already have #35 (moved), if we require just to modify our website to points to the ubuntu package we already have we will do it soon.

@strypey You know where we could find the match between Ubuntu and Trisquel versions? The doc about how is build says is based in Ubuntu without details.

https://en.wikipedia.org/wiki/Trisquel see Release history

Note that I hope that Trisquel will support Ubuntu 18.04 or 20.04 next year, because we will drop support for Ubuntu 16.04

mentioned in issue #35 (moved)

assigned to @smoubarik

@sblin Nex week @smoubarik will install Trisquel in a laptop and will test if the Ubuntu package works properly based in the provided link (https://en.wikipedia.org/wiki/Trisquel) and then she will inform here.

If it works this request we moved to our web page team.

added 1 deleted label

Perfect. In the ideal case, would be nice to contact Rubin for upstream packages, but it's another issue. https://trisquel.info/en/wiki/trisquel-team

Test

• OCI install (require apt update first, I did all using end user tools)
• OCI does not install the sources.list then will not get updates (To Do)
  • Commit: https://review.jami.net/c/ring-project/+/13187
  • Running test at https://jenkins.jami.net/view/packaging/job/packaging-testing-internal/195/

unassigned @smoubarik

assigned to @fpulido

Now the post install script run and adds the repository.

added Review label and removed 1 deleted label

Thanks for considering the request. The currently supported version is Trisquel 8 (Flidas), based off Ubuntu 16.04, which is supported by Ubuntu until 2021. Trisquel 9 (Etiona) is in beta testing as we speak, and is based off Ubuntu 18.04, which is supported by Ubuntu until 2023. I presume you plan to support each Ubuntu LTS version for as long as Ubuntu does? If so, then each version of Trisquel will also be supported during its active support period.

No, we only supports 2 Ubuntu LTS, so next year we drop 16.04

@sblin

No, we only supports 2 Ubuntu LTS, so next year we drop 16.04

OK. So Trisquel 8 will be supported by Jami until 20.04 comes out. I expect Trisquel 9 will be officially released by then, a bunch of the community are already running it as testers. Then work will begin on Trisquel 10. The aspiration is to release each Trisquel version 6 months after the Ubuntu LTS it's based off is released, but the last couple of versions have been delayed due to infrastructure and workflow upgrades going on behind the scenes.

assigned to @gheller and unassigned @fpulido

@gheller I give to you the ticket ownership, to get it in our website keep in mind that download links and snipped must to be same as Ubuntu 16.04.

As soon as it become published in the website you could close this Issue.

closed

mentioned in issue #44

Thanks so much for taking such rapid action on this! Such a thrill to see the Trisquel name and logo appear on your downloads page :)

I just tried to follow the manual instructions using 64-bit Trisquel 8.0. Everything seemed to be working until I got to:

sudo sh -c "echo 'deb [signed-by=/usr/share/keyrings/jami-archive-keyring.gpg] https://dl.jami.net/nightly/ubuntu_16.04/ ring main' > /etc/apt/sources.list.d/jami.list"

It didn't seem to do anything and I was left sitting on a ">" prompt. I checked my sources list and nothing seems to have been added. There may be something I don't understand here, but "sh" doesn't seem to be a program on my system, and I can't find anything called that in the Trisquel repos. Is there something missing in this command?

BTW it might make the instructions easier to follow if commands that span multiple lines are indented, or some other layout that makes it crystal clear which are separate commands and which are flowover lines?

what is the output for which sh?

@sblin

what is the output for which sh?

/bin/sh

I tried it again. This time instead of copy'n'pasting directly into the terminal, I pasted into Pluma (default GUI text editor), then copy'n'pasted from there into the terminal. This time it seems to have worked. It could be that something other than just the command was included in the copy from the download page? Most likely just some user error on my part. Sorry to bother you :{

np, I think the last quote was erased in your term :)

But yeah if sh is missing from your system, it's definitely not a GNU/Linux system or a really weird one.

Oh, one other thing, the instructions use "sudo apt install", so for consistency, the last line could be simplified to:

sudo apt update && sudo apt install jami

Thanks again for including us! Apologies for noobness :)

Running: sudo apt-get update && sudo apt-get install jami

OR: sudo apt update && sudo apt install jami

Produces this output:

    Reading package lists... Done

    Building dependency tree       

    Reading state information... Done

    Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.

    The following information may help to resolve the situation:

    The following packages have unmet dependencies:

    jami : Depends: libayatana-appindicator3-1 (>= 0.4.90) but it is not installable

    Depends: libgtk-3-0 (>= 3.21.5) but 3.18.9-1ubuntu3.3 is to be installed

    Depends: libqrencode4 (>= 3.2.0) but it is not installable

    Depends: libqt5core5a (>= 5.12.2) but 5.5.1+dfsg-16ubuntu7.6 is to be installed

    Depends: libstdc++6 (>= 9) but 5.4.0-6ubuntu1~16.04.12 is to be installed

    Depends: jami-daemon (= 20191128.1.4c44bb7~dfsg1-1) but it is not going to be installed

    E: Unable to correct problems, you have held broken packages.

EDIT: spaces added to improve legibility

@smoubarik what version did you use to test Trisquel?

Trisquel 8.0

trisquel 8

On my 32-bit laptop, also running Trisquel 8.0, I'm still using the repo I added before the rename to Jami: https://dl.ring.cx/ring-nightly/ubuntu_16.04

This seems to be working fine. The version of Jami currently installed on that laptop, from that repo, was built on 2019-11-29 02:22:29 UTC.

EDIT: for clarity

reopened

@fpulido just tried with a trisquel 8 from scratch. Working, so I close

closed

removed Review label

FYI the old Ring repo address I used to add Jami to my 32-bit laptop before the rename to Jami just stopped working: https://dl.ring.cx/ring-nightly/ubuntu_16.04

Error message is:

Err:9 https://dl.ring.cx/ring-nightly/ubuntu_16.04 ring Release server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

Two questions:

1. Can this be fixed at your end or do I need to remove it from my sources.list and replace it with the Jami address?
2. If I do need to change the repo source, do I need to uninstall Jami before I remove the Ring source, and reinstall from the new source, or will the new source be able to smoothly take over updates?

FYI the old Ring repo address I used to add Jami to my 32-bit laptop before the rename to Jami just stopped working: https://dl.ring.cx/ring-nightly/ubuntu_16.04

Error message is:

Err:9 https://dl.ring.cx/ring-nightly/ubuntu_16.04 ring Release server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

Two questions:

1. Can this be fixed at your end or do I need to remove it from my sources.list and replace it with the Jami address?
2. If I do need to change the repo source, do I need to uninstall Jami before I remove the Ring source, and reinstall from the new source, or will the new source be able to smoothly take over updates?

The Ring.cx repo source is working again now, thanks :)

Just editing the file in your souces.list should be enough. dl.jami.net is exactly the same server as dl.ring.cx. No need to uninstall and yes it's recommended

Just editing the file in your souces.list should be enough.

It wasn't in sources.list on my system, but I edited using the Software and Updates applet in the Preferences GUI and it seems to be working.

@sblin

@fpulido just tried with a trisquel 8 from scratch. Working, so I close

Did he follow the instructions on your website to the letter though? When I go to: https://jami.net/download-jami-linux/

... and click on the Trisquel logo, a one-click installer appears for Trisquel 8.0, which correctly provides a .deb targeted at a 16.04 base. But the manual instructions underneath tell me to add: https://dl.jami.net/nightly/ubuntu_19.10/

It appears this is what I did, which I presume is why it's not working. If I click the dropdown that specifies Trisquel 8.0, the manual instructions change to give the correct URL: https://dl.jami.net/nightly/ubuntu_16.04/

It appears your website still needs a little tweak to fix this, and I would appreciate you reopening the issue until this happens. Thanks for all your work on this, and sorry it's created a bunch of extra mucking around for you all.

I suppose that they change the manual instructions via JS :/

I'll indicate this to the website team

mentioned in issue #48 (closed)

added packaging label