Skip to content
Snippets Groups Projects
  1. May 12, 2021
  2. May 11, 2021
  3. May 04, 2021
    • Sébastien Blin's avatar
      misc: final cleanup for opensuse and debian · 47c61dff
      Sébastien Blin authored
      Change-Id: I07cf920ed99f460bffe1d8a16f3444706f4572c3
      47c61dff
    • Maxim Cournoyer's avatar
      packaging: Add jami-libqt to the jami-all package. · 4e969701
      Maxim Cournoyer authored and Sébastien Blin's avatar Sébastien Blin committed
      This makes the current 'jami-all' package the one used for the
      one-click install package.
      
      * packaging/rules/debian/rules (OCI_INSTALL_DIR): New variable.
      (override_dh_auto_install): Extend rule to install the files of the
      jami-libqt package.  Do not include the jami-gnome in jami-all.
      * packaging/rules/debian/control (jami-all): Update description.
      * packaging/rules/debian-one-click-install: Delete directory.
      * packaging/rules/debian-one-click-install/jami-all.postinst: Move to ...
      * packaging/rules/debian/jami-all.postinst: ... here.
      * scripts/make-packaging-target.py: Remove all OCI-specific targets.
      * scripts/deploy-packages.sh (package_deb) [jami-all]: Do not add
      package to the apt repository.
      [manual-download]: Look for the jami-all package from the main
      distribution directory, not in a '_oci' suffixed version.
      
      GitLab: jami-client-qt#263
      Change-Id: I4cacf26355c767d1c77b1ce478b184023481b674
      4e969701
  4. May 01, 2021
  5. Apr 19, 2021
  6. Feb 26, 2021
  7. Oct 15, 2020
    • Sandra Tobajas's avatar
      packaging: debian: use cross compilation for armhf platforms · d6dde7ee
      Sandra Tobajas authored
      Using qemu in user mode to build jami package for raspbian platforms
      adds a lot of overhead.
      
      Remove the virtualization using the Debian 10 cross-compiling toolchain.
      The target platform (i.e. the platform on which the package will be
      installed) has to be set and some compilation options has to be added in
      the debian/rules file.
      
      Also add the armhf architecture in the Docker container in order to
      install the package dependencies for this platform.
      
      Change-Id: Ic2282ad9377d52482bca4a4f0ef017fbcc1f8eb7
      d6dde7ee
  8. Aug 12, 2020
    • Andreas Traczyk's avatar
      add the qt client submodule · 5ec47bc3
      Andreas Traczyk authored and Sébastien Blin's avatar Sébastien Blin committed
      Replaces the ring-client-windows submodule with jami-client-qt and
      adjusts make-ring.py and helper scripts to support both the gtk and
      qt client builds for GNU/Linux.
      
      Gitlab: #581
      Change-Id: I55c0272cb354c9fa96f3541b6e5a8b7b271f14ba
      5ec47bc3
  9. Jan 13, 2020
    • Fredy Pulido's avatar
      packaging: adds debian 10 and raspbian arm · b20faf61
      Fredy Pulido authored and Sébastien Blin's avatar Sébastien Blin committed
      Adds:
      * Debian 9 armhf
      * Debian 9 arm64
      * Debian 10 armhf
      * Debian 10 arm64
      * Raspbian 10 armhf
      * The One Click Install (oci) version for all this items
      
      This commit also fix the --generate option in the generated makefile by
      scripts/make-packaging-target.py and remove the --architecture option
      there because was not used at any part of the script.
      
      Because our builder docker can not docker build with ARM we implemented
      a workaround called dirty qemu-static is documented and we have a issue
      to sovle it.
      
      The pipeline for packaging-deploy-gnulinux-generic got changed to add
      the support for the ARM architecture but the OCI build is not enabled
      because the build including the oci takes long (5 hours or plus).
      
      Warning: require companion changes in daemon (topic debian-arm)
      to ensure the right compilation flags
      
      Change-Id: I905bbd4660824670d7de836129886f3d7f1dc83b
      b20faf61
  10. Nov 15, 2019
  11. Nov 13, 2019
  12. Nov 12, 2019
  13. Nov 11, 2019
    • Fredy Pulido's avatar
      packaging: renaming packages from ring to jami · 553fef15
      Fredy Pulido authored
      This commit rename the tarball, debian, ubuntu and fedora packages.
      
      This commit also modify the debian post install script to add support
      our repositories for Debian 10 and Ubuntu 18.10 and 19.04 and create
      transition packages to ensure a proper nama transition in debian based
      distributions.
      
      Warning: when using reprepo to add the ring transition deb package
      this get into pool/main/j/jami. for now we think is a reprepo error
      because reads the Source: instead of Package: field.
      
      Change-Id: I47449a79c1a8bfd6ee0f3ffed618886f1dc1645a
      553fef15
  14. Apr 19, 2019
  15. Apr 15, 2019
  16. Apr 08, 2019
  17. Apr 05, 2019
  18. Mar 27, 2019
  19. Jan 02, 2019
  20. Oct 21, 2018
  21. Aug 17, 2018
    • Hugo Lefeuvre's avatar
      packaging: different releases for website · cd58aca8
      Hugo Lefeuvre authored
      It has been decided that we would have different releases between
      website and apt repository. The version from the website would have
      debian revision -0 and the one from apt repositories -1.
      
      The main difference resides in the fact that the version from the
      website distributes a postinst script which installs key and apt
      source.list so that Ring gets automatically updated when installed
      via one click install. This is not the case with the one from apt
      repos.
      
      Change-Id: I7bbfdfa41b0133ebe93f16bc550aa437c8ddfa6a
      cd58aca8
  22. Aug 16, 2018
  23. Aug 13, 2018
  24. Aug 09, 2018
  25. Aug 08, 2018
    • Hugo Lefeuvre's avatar
      packaging: fix oci regression (s/$OS/$ID/) · c4069bff
      Hugo Lefeuvre authored and Sébastien Blin's avatar Sébastien Blin committed
      
      f737fa7b introduced a major regression breaking ring-all's oci
      feature: incorrect $OS variable was used instead of $ID.
      
      Change-Id: Ice1866affa649cf7d3f560a9cb6d4a25ea5c1551
      Reviewed-by: default avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
      c4069bff
    • Hugo Lefeuvre's avatar
      packaging: fix issues with oci on Linux Mint · f737fa7b
      Hugo Lefeuvre authored and Adrien Béraud's avatar Adrien Béraud committed
      ring-all automatically registers
      
      dl.ring.cx/ring-nightly/{id}_{version_id}
      
      (id and version_id from os-release) as a trusted source. This is
      perfectly fine as long as the package is installed on an officially
      supported system, but if the package is installed on an unsupported
      system (e.g. Linux Mint) the installed source will be wrong even if
      even if the package is expected to work.
      
      This patch addresses this issue by adding if else if else statements
      handling all possible cases. This is not as pretty as before but it
      makes sure we handle all cases properly.
      
      Change-Id: I25167e013c56b212f7d59275419921cd0732de17
      Gitlab: #490
      f737fa7b
    • Hugo Lefeuvre's avatar
      packaging: build again ring client binary package · c79ae4d4
      Hugo Lefeuvre authored
      Recent packaging changes removed the ring binary package from ring.cx
      and replaced it by ring-all. This is because it doesn't make sense to
      most end users to install daemon and client separately. However this
      change has broken compatibility with the previous packaging policy, at
      the very least because we didn't provide a transition package.
      
      There are two solutions:
      1. Provide a transition package
      2. Build ring binary package again
      
      Both should work well but 2. has better compatibility with official
      Debian/Ubuntu packaging so we opt for this one.
      
      Change-Id: I556ae580126038de7077f91b137adbf1046d59e4
      c79ae4d4
  26. Aug 06, 2018
  27. Aug 02, 2018
  28. Jul 26, 2018
    • Hugo Lefeuvre's avatar
      packaging: Debian packaging update · 2ae32538
      Hugo Lefeuvre authored and Sébastien Blin's avatar Sébastien Blin committed
      
      Backport various fixes from Alexandre's work on the official Debian
      package:
      
      Debian packaging:
      * Add missing libqt5sql5-sqlite dependency
      * Various copyright updates
      * Update Standards-Version
      * Priority optional (extra is deprecated now)
      * Update Vcs-* fields
      * Add missing copyright entry
      * Remove useless gbp.conf file (only meaningful when using
        git-buildpackage in a git-buildpackage compatible repo which is
        not the case here)
      
      Packaging scripts:
      * Remove Ubuntu 14.04 and 15.10 related code
      * Various copyright updates
      * Set e-mail address before generating changelog entry
      
      Change-Id: I18e523422d16fe129cf6773ab01a99b00232a5bb
      Gitlab: #481
      Reviewed-by: default avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
      2ae32538
    • Hugo Lefeuvre's avatar
      packaging: install repo and keys · c902ea1b
      Hugo Lefeuvre authored and Sébastien Blin's avatar Sébastien Blin committed
      
      Currently it is very difficult for non-power-users to get Ring
      automatically updated when using the Debian package from the website.
      
      This is because configuring the Ring package repository requires
      command line operations.
      
      We want the Ring Debian/Ubuntu/whatever-Debian-based package (the
      one from the website, not the official one from the Debian archive)
      to make sure Ring's repository url and GnuPG key are installed as
      trusted source together with the binaries so that Ring gets
      transparently updated along with system updates.
      
      In order to do that, we have to change some things from the official
      package we have in the Debian archive:
      
      * we need to provide both daemon and client in a single ring-all
      package. Otherwise we will not be able to provide a one-click install
      (users would have to install daemon and client in two separate steps
      and that doesn't make much sense to non-geek users).
      
      So, replace ring by ring-all and keep building ring-daemon as before
      (we still want to provide daemon-only packages).
      
      * we need to add prerm and postinst scripts which will take care of
      installing the repo and keys (and this has to be done in different
      ways depending on the distribution) in the ring-all case.
      
      Also, remove transition package ring-gnome which has already
      disappeared from the Debian package some time ago.
      
      Change-Id: I34d5e5ba000d5d750c8db55c65b536a237a738b5
      Reviewed-by: default avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
      c902ea1b
  29. Apr 20, 2018
  30. Feb 26, 2018
  31. Dec 19, 2017
  32. Jul 06, 2017
Loading