Also add packages to .dockerignore, as this output directory can grow
to multiple GiBs.

Change-Id: I17b8b0a6d7be535d888232952c346b45c3224eb1

It was recording the Jenkins build workspace, which cannot be useful:

  root@jami-repovm-01:/srv/repository/ring/nightly# find -name options -exec cat {} +
  basedir /var/lib/jenkins/workspace/packaging-deploy-gnulinux-generic@2/ring-project/repositories/ubuntu_20.10
  basedir /var/lib/jenkins/workspace/packaging-deploy-gnulinux-generic@6/ring-project/repositories/debian_9
  basedir /var/lib/jenkins/workspace/packaging-deploy-gnulinux-generic@2/ring-project/repositories/ubuntu_17.04
  basedir /var/lib/jenkins/workspace/packaging-deploy-gnulinux-generic@5/ring-project/repositories/ubuntu_20.04
  basedir /var/lib/jenkins/workspace/packaging-deploy-gnulinux-generic@4/ring-project/repositories/ubuntu_16.04
  basedir /var/lib/jenkins/workspace/packaging-deploy-gnulinux-generic@2/ring-project/repositories/ubuntu_17.10
  basedir /var/lib/jenkins/workspace/packaging-deploy-gnulinux-generic@6/ring-project/repositories/raspbian_10
  basedir /var/lib/jenkins/workspace/packaging-deploy-gnulinux-generic/ring-project/repositories/ubuntu_19.04
  basedir /var/lib/jenkins/workspace/packaging-deploy-gnulinux-generic/ring-project/repositories/ubuntu_18.04
  basedir /var/lib/jenkins/workspace/packaging-deploy-gnulinux-generic@4/ring-project/repositories/ubuntu_18.10
  basedir /var/lib/jenkins/workspace/packaging-deploy-gnulinux-generic@4/ring-project/repositories/debian_10
  basedir /var/lib/jenkins/workspace/packaging-deploy-gnulinux-generic/ring-project/repositories/ubuntu_19.10

Change-Id: I3b50d78c8b2c084e2e510f5b37958762db9ff185

Repeating N times the same docstring hampers readability.  Output it
once as the generated file header.

Change-Id: Id5ae8caa35f478919a2233754b17db15a29e2cd0

Some tarballs are expensive to generate.  It's useful to be able to
reuse those.  The cleanup is moved to the clean target.

Change-Id: Ibe2b379be60dbb4b5c4eea9f0eeae4be84ccdb16

This hack is no longer necessary.  The Jenkins nodes are running Docker 19.

Change-Id: I8e41e1295a49ebe48b2fca9fa6c91158f49f16c9

Debian 9 packaging is removed as well, not because it is EOL, but
because it doesn't have the runtime required to run Jami (the daemon
requires C++17 but GCC 6 in Debian stretch doesn't support it).

A 'list-package-targets' Make target is also added; it'll be used by
the CI.

Change-Id: I87a26b14ea48bd17ebccb536f23a5f2637f28743

Change-Id: Ibfe20a56db762a844ed458d4bea1331051e0f0b5

Rename Makefile.packaging to Makefile, as it's the only one.
Makefile.packaging symlinks to it, to preserve backward compatibility
for now.

Change-Id: I136d01342e9779e9bb7a21b22dd10f54b6ac7064

Maxim Cournoyer authored 4 years ago and Sébastien Blin committed 4 years ago

The current target is not functional; the Gentoo packaging is
community maintained anyway.

Change-Id: I7dfe8641ccddb53ff1a448f2afaacaa591fc7dec

Restore required packages, and also add missing -DENABLE_STATIC=true
for client-qt.

Change-Id: I49997afa01109e1326ec06f06051504311f8471f

Adapt the main jami snapcraft.yaml file for client-qt, and move a copy
of the previous client-gnome snap to a new jami-gnome/ subdir.

Change-Id: If1e014c7af9d89c1fe3d13b5d365d74c0ecf368d

This reverts commit c59ff3b3.

Reason for revert: Breaks packaging on debian

Change-Id: Ia29ff90d7c2dba83d2831f5f81f004532f455311

Amin Bandali authored 4 years ago and Adrien Béraud committed 4 years ago

Change-Id: I0df659931adcd5d76912e3fbe2e48eeb4dcb32c1

- use cmake to build client-qt (client's cmake includes global installation support)
- copy-runtime-files.py is no longer necessary since it is directly managed by cmake
- uninstall revision: use make uninstall rule for lrc, client-qt and client-gnome
- add doxygen and graphviz dependencies for building documentation

Change-Id: I3fb1d56cb80556337b2c10fda1a67f84c290158c

Change-Id: I9df8043ec2da9c2a0c4ba3a2e09e5feadb71e585

Frisbee Whisperwind authored 4 years ago and Amin Bandali committed 4 years ago

- remove extra print statement
- add dependency qt5-tools

Change-Id: I280a41e504557a7fcaf8f862bcef72432edbf473

Without libssl-dev available in build time, we would fall back on
building our own from a locally-built libressl, which would have
incorrect paths for location of certificates: the resulting snap
would incorrectly try to look for certificates under
parts/jami/build/daemon/contrib/x86_64-linux-gnu/etc/ssl, which is
not available after build, instead of a more sensible /etc/ssl.

Change-Id: I76cb847d18561e29250d4b9d39d1993dabc9a864

Change-Id: Ibfe182c5d8d5658603b1c4ee169b750e376ebc57

GitLab: #1127
Change-Id: I8190ea8b974a44b7851969cdb5d33bd32074ddd9

Amin Bandali authored 4 years ago and Sébastien Blin committed 4 years ago

Change-Id: I309f31ba1d23a9cbc48e2936b7591ae4fba40a76

Change-Id: Iee3340020b7507e0098a38463e12907350c9a055

Change-Id: I9e8e666f09949d56c3c14c43b834f1d39c10c9db

Change-Id: If96860fed6a232566b04d131b84f4ce847399572

Change-Id: I6a794b638cffc66cb18924ca0fcf5be0a0fcb987

Change-Id: Ide3c5fcc8d261c3a517c07501019166b7dad45c8

Albert Babí Oller authored 4 years ago and Albert Babí Oller committed 4 years ago

- add dependencies for building client Qt
- avoid forcing build with local Qt when no path is specified (linux)
- verify system's Qt version before building lrc + client-qt

Change-Id: I18b51647044c1f15358595710f51a88618de41f5

Change-Id: I5b24b809cec3763c44808fe9f056cba862336531

Change-Id: I56de10fdfb39d14405cb0e502c472b4dbc112dc0

Currently libtasn builds as part of gnutls. When building
with clang 12 asn1_der_coding return an error ASN1_VALUE_NOT_VALID
when parsing time. This patch add libtasn to dependencies to
use prebuilt version.

Change-Id: I424ea58a3c89981e8c3a781c9cbd66fc429f919b

Also remove some warnings in make-ring.py

Change-Id: I8fabab27a33e94a9a0eabcce4e22cdf760bc8e05

Change-Id: I96b1cd8ce6cdf134f93b2d6d6742dabdf28d0842

Sébastien Blin authored 4 years ago and Adrien Béraud committed 4 years ago

Change-Id: I5a43f4ca5d0c8e43b3f73cb028aeb38c31b16342

Change-Id: I3a8ca39f46eb6514427969bd697084e2ddfb4a50

Sébastien Blin authored 4 years ago and Adrien Béraud committed 4 years ago

Fix build for opensuse 15.1
Add build for opensuse 15.2 and tumbleweed

Change-Id: I561a6f48dc4674efd0a9e83a20bb238d476d29a6

Albert Babí Oller authored 4 years ago and Albert Babí Oller committed 4 years ago

Change-Id: Icf38cabf03709802dea4e13369b70f7d584f65f8

Change-Id: Ia5fd11c87ba29ba4a1305a67e90c00004404ac13

Ming Rui Zhang authored 4 years ago and Andreas Traczyk committed 4 years ago

Change-Id: Ibd9eab86af0dbe5a7f1349ff084afb46e85f370d

Change-Id: I6fe7da475e0004278382c4d5a996568557829bf4

As the packaging for raspbian platform does use the virtualization with
qemu in user mode, remove the qemu binaries in the build container.

Change-Id: Id72ca6bad3d47d525c3a7d0213d5fc5eebbaa3d4

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