Change-Id: Ibbafa6556bcf75965bd27ab44da5ee372ea872b0

Change-Id: Ic287222683ff572e1d442cd36ce8cc106c35c1f1

Change-Id: Ia039569e74cce6cf2d15a6e36849cad9b3b9d489

Change-Id: I996b402c5eb9b03ea18a0309818c6a52c9d6e236

Change-Id: Ic287222683ff572e1d442cd36ce8cc106c35c1f1

Change-Id: I2e5736d4304bb841c8ec86d883b7bc0641669881

* Makefile (QT_PATCH): Bump up to 2.
(QT_TARBALL_CHECKSUM): Update to Qt 6.2.2 release tarball's sha256sum.
* docker/Dockerfile_ubuntu_18.04: Move the nodejs installation earlier
in the Dockerfile, as it needs to already be installed by the time we
want to install libqt-jami's build dependencies.
* packaging/rules/debian-qt/control (libqt-jami) <Build-Depends>: Add
missing nodejs (>= 10.19) dependency.

jami-packaging#111
Change-Id: Ie15a1f4c7cfb274dc6a1784ce41f5b7383002abe

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

* docker/Dockerfile_opensuse-leap_15.3: The 'opensuse/leap:15.3'
docker image doesn't seem to have gcc11, so use gcc10 instead.
* packaging/rules/rpm/jami-gnome.spec: Unconditionally require
'make' for build, and require 'cmake' only where a recent enough
version is available in the distro (otherwise, we grab and use
external cmake e.g. using 'scripts/install-cmake.sh').

jami-packaging#111


Co-authored-by: Amin Bandali <amin.bandali@savoirfairelinux.com>
Change-Id: I5686f8e5d77eb8108b1581a33a2432006a1a688b

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

The recently introduced 'guix shell' command automatically manages a
cached profile for us; prefer it to 'guix environment', and do away
with a channels file, given fixes in Guix have now been incorporated
in the main branch.

* Makefile (portable-release-tarball)<guix environment>: Replace by
'guix shell'.
* build.py (run_dependencies)[guix]: Likewise, and do not use a
channels.scm file.
(run_install): Likewise, and provide a hint when TARBALLS is not set.
* guix/channels.scm: Delete file.
* guix/manifest.scm: Adjust comment.

Change-Id: I50ca99e51f0ebca136c9bbc5a0ca3063075432b4

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

The top level tarball directory was renamed from ring-project to
jami-project in commit 21d9f320.

Automated via:
  $ git grep -l ring-project | xargs sed -i 's/ring-project/jami-project/g'

Change-Id: I4c0f01cca94d06c536fc1d75bf608e5728d41b31

Change-Id: Iacf9fd55b6a8cfc3521df1c10cb99192de8ae536

* Makefile.packaging: Delete file.
* make-ring.py: Likewise.

Change-Id: Icc243592651374d208021b5713ed4fda5a4a537c

Change-Id: I2c7ae1349a69fb24f65ea435fa57fa7cc547c631

Previously, the Jenkinsfile did not publish anything except for the
repositories: the release tarball would not get copied to
https://dl.jami.net for stable channel, and no commit nor tag would be
published for the release.

This change addresses these shortcomings with the following changes:

1. Tarballs can be published for the stable channel.
2. Release commits/tags can be published to their corresponding
branch (stable/nightly).

The RELEASE_VERSION string is also once again derived in a
deterministic fashion, from the date of the last commit.

* Jenkinsfile (SSH_PRIVATE_KEY): Remove variable.
(RING_PUBLIC_KEY_FINGERPRINT): Rename to...
(JAMI_PUBLIC_KEY_FINGERPRINT): ... this.
(GIT_USER_EMAIL, GIT_USER_NAME, GIT_PUSH_URL)
(JENKINS_SSH_KEY, DL_SSH_KEY): New variables.
(params.DEPLOY): Fix description.
(Checkout channel branch): New stage.
(Generate release tarball): Also commit and tag.
(Publish release artifacts): New stage to publish conditionally based on the
DEPLOY parameter and the selected channel.
(Sign & deploy packages): Use the 'sshagent' step to setup SSH access.
<--remote-ssh-identity-file>: Remove argument.
<--keyid>: Adjust variable name.
* scripts/deploy-packages.sh (package_snap): Simplify.

Change-Id: I9008ecc2a4ef9820dbc96e26c966ae72110d897d

jami-client-qt#601

Change-Id: Ia0faab2f07c11b0bac14098aa73a75bf2c41d979

GitLab: #1371
Change-Id: Iaa825b8b0bc090d88c645f2953c897e07a6bc710

tumbleweed is broken since months (zypper crashes on the docker image)
and no issue remounted, also we support guix and snap for this platforms.

Change-Id: I0de908ba91eeeaf42c0d2599b3d69924fbcb7920

https: //git.jami.net/savoirfairelinux/jami-packaging/-/issues/111
Change-Id: I481e71d9650ce738c3211448aadd1d93478d84dc

Kateryna Kostiuk authored 3 years ago and Sébastien Blin committed 3 years ago

Change-Id: I7e44b91981702be83f4dd848c513d16d3dcc9f88

Ming Rui Zhang authored 3 years ago and Sébastien Blin committed 3 years ago

Change-Id: Id48d3b322171f7e8fe1b240f37f10e9e5843530e

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

Previously, the Jenkinsfile did not publish anything except from the
repositories: tarballs would not get copied to https://dl.jami.net for
the nighty and stable channels, and no commit nor tag would be
published for the release.

This change addresses these shortcomings with the following changes:

1. Tarballs are produced for the nightly and stable channels, and
organized in a sub-directory matching their channel name.
2. Release commits are made to their corresponding
channel (stable/nightly).
3. Stable releases are also tagged with 'YYYYmmdd.$day_commits_count.$commit_id'.

* Jenkinsfile (SSH_PRIVATE_KEY): Remove variable.
(RING_PUBLIC_KEY_FINGERPRINT): Rename to...
(JAMI_PUBLIC_KEY_FINGERPRINT): ... this.
(GIT_USER_EMAIL, SSH_CRED_ID): New variables.
(params.DEPLOY): Fix description.
(Checkout channel branch): New stage.
(Generate release tarball): Also commit and tag.
(Publish release artifacts): New stage to publish conditionally based on the
DEPLOY parameter and the selected channel.
(Sign & deploy packages): Use the 'sshagent' step to setup SSH access.
<--remote-ssh-identity-file>: Remove argument.
* scripts/deploy-packages.sh (package_snap): Simplify.

Change-Id: I9008ecc2a4ef9820dbc96e26c966ae72110d897d

else version seems broken.

Change-Id: I4059b4dfa752d4c608eafc485867af28f1232602

Change-Id: I8d78545a23e75d7d9ca016eb00cea3e3094c73ac

debhelper on ubuntu 21 is bugguy and introduced LTO bugs
Some similar issues:
https://bugreports.qt.io/browse/QTBUG-98805
https://www.mail-archive.com/lfs-support@lists.linuxfromscratch.org/msg06950.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48200#c46
https://github.com/rhboot/efivar/issues/156
Disabling lto flags for daemon fix this issue.

Change-Id: I7c666c9e3d33f659c781a4bf68debf367a451a88