A variable had not been renamed properly, causing an unbound variable
exception to be thrown.

* Jenkinsfile ('Sign & deploy packages') <target>: Rename variable to ...
<distribution> in the later loop.

Change-Id: I6c92b3249b537a91cec58438bfbcf8780043d74e

The deb-pack targets build a Guix pack of the jami-qt client in the
.deb format, ready to be installed on any dpkg-based GNU/Linux
distribution.

* Makefile (RELEASE_VERSION, RELEASE_TARBALL_FILENAME): Export
variables.
(has-guix-p): New target, to be used as a predicate.
(portable-release-tarball): Rewrite in terms of the above.
(SUPPORTED_GNU_ARCHS, DEB_PACKS, DEB_PACK_TARGETS): New variables.
(guix-pack-command, define-deb-pack-rule): Likewise.
(deb-pack-x86_64, deb-pack-i686): New targets.
(PACKAGE-TARGETS): Register them.
* guix/guix-pack-manifest.scm: New file.
* guix/guix-pack-deb.postinst: Likewise.
* guix/manifest.scm: Specify qtbase to be at version 5, as Guix now
has version 6 too.
* packaging/rules/debian/jami-all.postinst: Harmonize.
* scripts/deploy-packages.sh (package): Simplify and register the
'guix-deb-pack' distribution.
* Jenkinsfile (Sign & deploy packages): Simplify to deploy all the
packages subdirectories.  This makes it easier to handle multi-arch
packages for the same distribution, and removes the need to encode the
distribution information in the target name.

Change-Id: Id6f69e7a5872a39b4b8f50fa09c8ec3475e9c896

Change-Id: Ib091e768b3d408c1f5b4552ae40c5cf502d928dd

https://review.jami.net/c/jami-client-qt/+/19283 recently marked
Python 3 as a required build depdendency for building client-qt,
as it's needeed for generating 'resources.qrc' in build time.

Change-Id: Ib7eb3822ec5af5e4223d8a05b52d7cb5bb22e8d5

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

This should prevent errors like:

E: Repository 'http://deb.debian.org/debian testing InRelease' changed
its 'Codename' value from 'bullseye' to 'bookworm'

Change-Id: If3834c2a81bc084d79b706eb8714b04189698a90

Change-Id: I195452f1b14a835d08b4e1be734b7a9bd880ef8a

Change-Id: I69acb6477c054be46357eba3b7ee5bf286fd108b

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

* packaging/rules/debian/rules (override_dh_auto_configure): Move
recipes to ...
(override_dh_auto_configure_build): ... here.  This is necessary as
the LRC now must find the share library of the daemon, hence it must
be built before the LRC configuration occurs.
<-DENABLE_LIBWRAP=true>: New option when configuring the LRC.
* packaging/rules/rpm/jami-libclient.spec (%build): Likewise.
* scripts/install.sh (lrc_cmake_flags): Likewise.
(OSTYPE): Remove variable.
(sharedLib): Remove variable.  The Jami daemon shared library is
needed when dynamically linking against it when libwrap is enabled.
* packaging/rules/rpm/jami-daemon.spec (%build): Drop the --disable-shared
option.
(%files): Register the libring.so dynamic library.
* packaging/rules/debian/rules (override_dh_auto_configure): Drop the
--disable-shared option.

GitLab: jami-packaging#101
Change-Id: Id1acaaf15a0f3d561c73bf34dde48f4eaf058eed

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

This reverts commit 62f547b5.  The fix
now more properly lives in the contrib build system.

Change-Id: I7bb7d1f302c91be46627fc26eddece1d768fb308

Change-Id: Icc26fef916e323d87247abac8d45f7e55bc100e8

Change-Id: I5cf9c056fb02c9547679f021759b77e7242c58c0

Change-Id: Ia05c157c01cd231eb7902e634906a8387baefb87

The repositories were renamed on review.jami.net recently.

Change-Id: I094e83a51cd507f3e03fdf3ca5a77203509a8afc

CMake 3.10 in Ubuntu 18.04 has a bug where it finds Python 2 even when
Python 3 is present.  Install 3.12, where the bug is fixed.

* docker/Dockerfile_ubuntu_18.04: Download, check and extract CMake
3.12 to /usr/local.

Change-Id: I8e344e630cfcdc58d8e3579ac0b7c22314264ab9

* packaging/rules/rpm/jami-daemon.spec (%files): Remove jami_contact.h header.

Change-Id: If13ca9d29a4bd65066857a9bce7e3b44379515cb

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

* packaging/rules/debian/rules (override_dh_auto_build): Invoke the
contrib build system with GTKDOCIZE set to false to workaround
https://savannah.gnu.org/support/?110503 present in Debian unstable.

Change-Id: I03e6d070d33fb126e3777517b6b4f1b4f042e315

Change-Id: I0a1d2e42a255371ff8efbc943f72dc2ceeaf88cd

* packaging/rules/debian/rules (LDFLAGS): Filter out the
-Bsymbolic-functions linker option added by default on Ubuntu.
[ubuntu_21.04]: Do not force the bundling of FFmpeg.

Change-Id: Ia83c305808072a4e5923530421924eb85f9b5b5e

As it is not necessary.

Change-Id: Ic58236dc0da3c24a090c9f05437482b46892f6c5

Change-Id: I9ed56eee9cc52a6423af3daafa3b57b494481e03

Change-Id: Id592bc760b5ae10f74ed13c47ba7602f633d80e3

Change-Id: I4a03364f4062379fe8dc849ba02343d14de730f9

This give us more controls about bugs and anyway, we're going to
use Qt 6.2 for macOS support.

Change-Id: I78c17a9984248b4dad08ab2091532159335d4c97

Maxim Cournoyer authored 3 years ago and Amin Bandali committed 3 years ago

Prior to this change, the Makefile packaging targets were generated by
a Python script, supposedly to reduce boilerplate.  Make is able to
programmatically define rules, so use its features instead.

The packaging targets 'package-' prefix is dropped, making the targets
names match the distribution directly, such as 'ubuntu_20.04'.

The docker *-ro bind mounts are dropped; instead only the release
tarball file name is exposed to the containers as *the* source, which
makes it unambiguous as to which sources are used.

The files related to RHEL builds are removed, as the RHEL build is
known to be broken and isn't being used.

* Makefile (DISTRIBUTIONS): New variable.
(make-docker-package-target): New function.
(docker/Dockerfile-snap): Adjust accordingly.
docker/*: Standardize to use hyphens instead of a mix of hyphens and
underscores.
* docker/Dockerfile_rhel_8: Delete file.
* docker/profile-seccomp-fedora_28.json: Delete file.
* scripts/make-packaging-target.py: Delete file.
* Jenkinsfile: Adjust accordingly.

Change-Id: I2dc42b489a54b177ad038398a9d23a2a7e3007ec

The hash for client-uwp from last commit doesn't seem to exist on the
server, thus causing problems.

Change-Id: Id3ef70cc87a4326de2afbe6d5aefed470c4721f4

Maxim Cournoyer authored 3 years ago and Amin Bandali committed 3 years ago

Change-Id: I99a20bcf357032a6fcf689265c93670dcf65b8b7

Change-Id: I10a69b2026f6e6aa963ffaa95702c0c58c39d216

Change-Id: I8e6f99f0322d8787c8991228bdd6681b950b6a19

Change-Id: I9a18124056477b3552ebd0c4cb16117d1600497c

Change-Id: I168d713a885c9bb02ff405ac35d60373147ca597

Maxim Cournoyer authored 3 years ago and Maxim Cournoyer committed 3 years ago

* Makefile (portable-release-tarball): Do expose SSL_CERT_FILE
directly; expose SSL_CERT_DIR as /etc/ssl/certs instead, which is
where GnuTLS (hence wget) looks.

Change-Id: If827b33134a0846317efc0034ed27bd122334e23

The old 'createrepo' has been deprecated and is no longer offered in
current distributions.  Its replacement should be mostly backward
compatible.

* scripts/deploy-packages.sh: List requirements.
(enabled)<createrepo>: Adjust to use createrepo_c'.

Change-Id: Ie3e658dd1ea685558b07d6c9b969be7ad3a98050

Maxim Cournoyer authored 3 years ago and Maxim Cournoyer committed 3 years ago

* Jenkinsfile ('Check configuration'): Rewrite stage as a script.
This makes the stage show as passed instead of skip in Blue Ocean,
which is more accurate.

Change-Id: I5be0cdc0c918521c3580b60261b98b9dff804876

Automated via: $ git grep -l dring | xargs sed -i 's/dring/jamid/g'

Change-Id: I67715a37e0fae42a0e4d9ce42bd01becc1ac77f5

Otherwise the pipeline cannot be meaningfully used as a validation
job, as it'd always return success, even upon encountering one or more
build failures.

* Jenkinsfile: In case a packaging target failed building, set the
build result to failure.

Change-Id: I47c8b09936b088b27a02173aa94a0adb0f04dcb4

* Makefile (TAR_REPRODUCIBILITY_OPTIONS): New variable.
$(RELEASE_TARBALL_FILENAME): Invoke tar with the above options.
Invoke gzip with '--no-name', to prevent keeping the file name and
time stamp.

Change-Id: I64cac307c69cbfbdb7132b1f567f1c3f18baad8c

Properties is a scripted pipeline concept and doesn't work correctly
in the context of a *declarative* pipeline.

* Jenkinsfile: Add 'ansicolor' to the list of requirements in the top
comment.
(properties): Remove.
(triggers): New directive.

Change-Id: Idceff87a005a935ff6af2931fd0ed466d0e73911

This is a follow up to the f0fb8148ba7f453d73e31e1cece2dcffae68e878
commit (Use the PROGSHAREDIR macro to refer to the custom datadir) in
the daemon, that moved the ringtones from a hard-coded location of
/usr/share/ring/ringtones to $datadir/jami/ringtones.

* packaging/rules/rpm/jami-daemon.spec (%files): Adjust accordingly.
* scripts/install.sh (client_cmake_flags) <DRINGTONE_DIR>: Likewise.

Change-Id: Ia9d3403f5600a4ab4eefe28ee20611afc3f5e8b0

* build.py (run_run) <dring>: Adjust file name.
* packaging/rules/rpm/jami-daemon.spec (%install): Likewise.

Change-Id: Iedc4e0803bda19d139b29a4ccc669dcc8cc3fb9f

This is a follow up to commit 4ee93922, which introduced partial
deployments.

The unstash operation also needs to be handled specially, as it may
now fail attempting to unstash an item that could not be stashed
previously.

* Jenkinsfile ('Sign & deploy packages'): Skip target deployment when
it fails to be unstashed.

Change-Id: I59341e4c3bb007125402f4b28979d0e8e963757d