jami-packaging issueshttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues2022-12-29T16:37:38Zhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/125Repo name on Fedora2022-12-29T16:37:38ZSébastien BlinRepo name on Fedorahttps://dl.jami.net/nightly/fedora_35/jami-nightly.repo
=> Will show Jami 35, which means nothinghttps://dl.jami.net/nightly/fedora_35/jami-nightly.repo
=> Will show Jami 35, which means nothinghttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/85Fedora stable repository serves nightly builds2021-12-28T21:25:34ZFedora stable repository serves nightly buildsThe stable repository for Fedora serves nightly builds instead of stable release builds.
https://dl.jami.net/stable/fedora_31/The stable repository for Fedora serves nightly builds instead of stable release builds.
https://dl.jami.net/stable/fedora_31/Maxim CournoyerMaxim Cournoyerhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/31packaging-release .repo should contains dl.jami.net/stable2021-12-28T21:15:48ZSébastien Blinpackaging-release .repo should contains dl.jami.net/stablecf https://dl.jami.net/stable/fedora_30/ring-nightly.repo (contains -nightly)cf https://dl.jami.net/stable/fedora_30/ring-nightly.repo (contains -nightly)https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/60One click install for Fedora RPMs2021-05-04T13:44:56ZFredy PulidoOne click install for Fedora RPMsSame as #21 but for FedoraSame as #21 but for FedoraIgor StegarescuIgor Stegarescuhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/68jami-all.postinst - to avoid duplicates, use only one .jami-all.postinst for ...2021-05-04T13:42:32ZIgor Stegarescujami-all.postinst - to avoid duplicates, use only one .jami-all.postinst for rpm packages(Rhel,Fedora,Opensuse)Now each rpm distribution is using it's own jami-all.postinst , the scope is to config all rpm distributions to use one script jami-all.postinst to avoid duplicates.Now each rpm distribution is using it's own jami-all.postinst , the scope is to config all rpm distributions to use one script jami-all.postinst to avoid duplicates.PackagingIgor StegarescuIgor Stegarescuhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/88Packaging: add fedora 342021-04-19T13:21:40ZSébastien BlinPackaging: add fedora 34Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/4Fedora: dnf rename repo to jami2021-03-02T18:46:39ZSébastien BlinFedora: dnf rename repo to jami```
sudo dnf update
Ring 30 - x86_64 - ring
```
`https://dl.jami.net/nightly/fedora_31/ring-nightly.repo` must to be renamed as `https://dl.jami.net/nightly/fedora_31/jami-nightly.repo` in our website download instructions...```
sudo dnf update
Ring 30 - x86_64 - ring
```
`https://dl.jami.net/nightly/fedora_31/ring-nightly.repo` must to be renamed as `https://dl.jami.net/nightly/fedora_31/jami-nightly.repo` in our website download instructions then (my guess) you must to ensure the same file with both names to **do not brake repos people added before**.Maxim CournoyerMaxim Cournoyerhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/21One click install for Redhat RPMs2020-01-22T12:33:19ZSébastien BlinOne click install for Redhat RPMsThis seems possible, so we should do that :) https://opensuse-guide.org/installpackage.php
**One click Install (oci)** is a package that contains:
* Jami and his daemon in the same package
* A post installation script that add Jami's re...This seems possible, so we should do that :) https://opensuse-guide.org/installpackage.php
**One click Install (oci)** is a package that contains:
* Jami and his daemon in the same package
* A post installation script that add Jami's repository in the equivalent to `sources.list.d`
As reference in Debian we did it this way:
* We added `jami-all` package that contains Jami and his daemon (this get also published in the repository)
* Another package almost equal to `jami-all` that include the postinstall script
Then the use case flow is this:
1. Our user go to our website and download the OCI package
2. Our user click on the downloaded file and install Jami
3. During the installation Jami add the repository for futures updates
4. If the user update jami, or all the non updated packages in his distribution then Jami get updated.Sébastien BlinIgor StegarescuSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/23Fedora: rename fedora 31 pkg from Ring to Jami2019-11-11T21:37:57ZFredy PulidoFedora: rename fedora 31 pkg from Ring to JamiFedora 31 package must to be renamed from Ring to Jami
Important:
* Start your work over Igor's commit: https://review.jami.net/c/ring-project/+/12832
* You can take as reference Fedora related changes at https://review.jami.net/c/ring-...Fedora 31 package must to be renamed from Ring to Jami
Important:
* Start your work over Igor's commit: https://review.jami.net/c/ring-project/+/12832
* You can take as reference Fedora related changes at https://review.jami.net/c/ring-project/+/12774
Definition of done:
* Fedora package named jami must to be crated and published by jenkins in our internal repo
Keep in mind that using yum the package name must to be jami.PackagingSiham MoubarikSiham Moubarikhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/17Fedora: adds pkgs for fedora 312019-11-08T16:53:54ZFredy PulidoFedora: adds pkgs for fedora 31Use existing scripts and CI
Expected: running internal packaging in Jenkins must to generate fedora 31 pkgs. Jami must to work when installing this packages in a fedora 31.Use existing scripts and CI
Expected: running internal packaging in Jenkins must to generate fedora 31 pkgs. Jami must to work when installing this packages in a fedora 31.PackagingSiham MoubarikSiham Moubarik