Change-Id: Iadb4c2091913c670e977c1966ccc22f962d787a1

Since for our deb packages all the binary packages share the same
source package, and are built in the same environment, depending on
the distro and dpkg tools versions, dpkg-shlibdeps might incorrectly
add the wrong libclient package for either clients.  For example,
have the jami-gnome package depend on both jami-libclient-gnome and
jami-libclient; which is wrong, since jami-libclient-gnome and
jami-libclient conflict with each other and cannot be installed
simultaneously.  So, we instruct dpkg-shlibdeps to exclude the two
libclient packages from ${shlibs:Depends}, which is fine because
we already manually add the correct one to each client's Depends.

Also, use the system libarchive-dev package for Ubuntu 18.04 as well;
since like with Debian 10, building libarchive from daemon's contribs
fails there too.

GitLab: #1415
Change-Id: I1c065a7fd3fc58324c7893d5d23039f2a5109931

After the recent merge of the video renderer changes into lrc and
client-qt, the build for client-gnome is currently broken because it
has not yet been updated to follow the new API, a non-trivial task.
Thus, we add a separate lrc-gnome submodule for use by client-gnome,
as a temporary measure until the future vendoring of lrc into the two
clients.

With this change, the users of the Qt client ('jami' package) would
continue using 'jami-libclient' as a dependency, whereas for users of
the GNOME client ('jami-gnome') they would install and use the new
'jami-libclient-gnome' package.

Change-Id: I6aacb6c495c9a2953c328f2e9bfe6acd2b8cc645

Change-Id: I996b402c5eb9b03ea18a0309818c6a52c9d6e236

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

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

Change-Id: Icc26fef916e323d87247abac8d45f7e55bc100e8

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

Change-Id: I67715a37e0fae42a0e4d9ce42bd01becc1ac77f5

Change-Id: Ib2bd0ab1db50192da377b8807730ae95b0259e50

Change-Id: If3512d8c56cb19622f72c6245f6c04c411b719e2

Change-Id: I07cf920ed99f460bffe1d8a16f3444706f4572c3

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

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

Remove commented code and deprecated packages (it's bee more than a
year).

Change-Id: Ie7224c831405c07a33018ccc951a73bc05a93599

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

Also remove unused DEBIAN_PACKAGING_OVERRIDE.

Change-Id: Ida109a811bebd1fb46fd1a8b90fb5463518382c0

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

Change-Id: I5b89c33b6fb8b85df3307d517c0d55e35c5f02e2

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

Change-Id: I4022846de7e0fa1f2a3bf14ffe0a961920379580

Add missing libqt5sql5-sqlite entry to the ring binary package
dependencies. This bug was fixed in 2ae32538 and reintroduced later.

Change-Id: If8cfe0a09aca5c52c14fb352190be15134c503c7
Gitlab: #925

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

Change-Id: Icaeb11be9dd76c815150ec29ebad9cf0534a2144

Change-Id: Ica9cd2730d01da54d39b2be62f327876bff14f3e

Hugo Lefeuvre authored 6 years ago and Sébastien Blin committed 6 years ago

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: Sebastien Blin <sebastien.blin@savoirfairelinux.com>

Hugo Lefeuvre authored 6 years ago and Sébastien Blin committed 6 years ago

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: Sebastien Blin <sebastien.blin@savoirfairelinux.com>

aviau authored 6 years ago and Sébastien Blin committed 6 years ago

As of:
 - https://gerrit-ring.savoirfairelinux.com/9288



It is now prefered to build with libayatana-appindicator3-dev.

Change-Id: Ic42e019ada326a11d9c087558838374a1c75f652
Reviewed-by: Sebastien Blin <sebastien.blin@savoirfairelinux.com>

Lubomir Rintel authored 7 years ago and Guillaume Roguez committed 7 years ago

libnm-glib has been deprecated for three years and is eventually
going to disappear.

[GR: update Debian/Ubuntu deps as well and all docker files]

Change-Id: I60a9b1a37098715ac55d5fee6718883d2a55fe3c
Reviewed-by: Guillaume Roguez <guillaume.roguez@savoirfairelinux.com>
Signed-off-by: Guillaume Roguez <guillaume.roguez@savoirfairelinux.com>

Adds libvdpau dev package to dependencies for linux distros. Depends
on https://gerrit-ring.savoirfairelinux.com/5473/

Change-Id: I1cb33adf5707eb5bdf6efe998ecc6dde5b6ae909

Change-Id: I31de9b38a0433e4cd3e524624871da157a5a9a09
Reviewed-by: Guillaume Roguez <guillaume.roguez@savoirfairelinux.com>

Change-Id: If7fc608364f3dc9ea0d08650a4efc34756d61c63
Reviewed-by: Stepan Salenikovich <stepan.salenikovich@savoirfairelinux.com>

This is needed to build video HW acceleration code.
Dockers, packaging deps and make-ring.py changed by this patch.

Change-Id: Ia6c50aacc8a0f36db36b05c66bcd2db75291bce9

libsrtp is used by pjproject, but it is built as part of pjproject

Reviewed-by: Alexandre Viau <alexandre.viau@savoirfairelinux.com>
Change-Id: I809b028cc07e4f8d43273087f1a263e5ae02e72b

Change-Id: I943cefb8ec325c740190b679ca27d6d5bcae897a
Tuleap: #872

Added as client build dependency and to docker images.

Change-Id: I169e039446b7688bc52ec3619c93e1ce65089cee
Tuleap: #845
Reviewed-by: Alexandre Viau <alexandre.viau@savoirfairelinux.com>

This imports some of the changes made in the official Debian packaging
repository: https://anonscm.debian.org/cgit/pkg-voip/ring.git

- Don't run containers in interactive mode, which would require a TTY

- Build LRC with Debug symbols

- Build with V=1 to allow parsing logs

- Reorganize dependencies

- Try fetch-all three times before giving up

- Removed ubuntu15.04 references

Tuleap: #858
Change-Id: If0a81b15230a31d120982e113e695443262568e3

This moves the official Debian packaging into ring-project. Jenkins
should now be able to run packaging jobs and publish packages. It
should also make it easy to add a `verify` check on Jenkins to test
packaging patches.

This will make it much easier to work on packaging issues because the
build environment is now reproductible on any machine.

The patch adds Makefile targets to create packages such as:
 - package-all
 - package-<DISTRO>

Builds are all done inside Docker containers and it is possible to
build many at a time with the `package-all` target.

To debug a build, use `package-<DISTRO>-interactive` to obtain a shell
inside a container, ready to launch a build.

Tuleap: #781
Change-Id: Id87a74a6c412ffc5bf82b9562639ce5a9424b06a