Debian: repo rename from ring to jami

changed milestone to %Packaging

assigned to @fpulido

changed milestone to %Packaging

changed the description

Requires to modify:

• scripts/deploy-packages.sh

changed the description

mentioned in issue #5 (moved)

added 1 deleted label

added 1 deleted label and removed 1 deleted label

Debian

Doc: https://wiki.debian.org/DebianRepository/SetupWithReprepro

deploy-packages.sh (notes)

• Weird use of Codename: field, instead of buster, sid ... we have ring
• Install old packge and then Verify potential brakes for old users updating to the new one.

Related with:

• https://git.jami.net/savoirfairelinux/jami.net/issues/65
• https://git.jami.net/savoirfairelinux/jami-packaging/snippets/280

Changes in deploy script for debian based: https://review.jami.net/c/ring-project/+/12856

It passes the CI but I'm a bit blocked here because we can not just do symlinks to get the old repo working.

https://dl.jami.net/ring-internal/debian_10/dists/jami/InRelease

added 1 deleted label and removed 1 deleted label

changed title from Rename repos (but do not break old names!) to Rename repos links (but do not break old names!)

Debian Readme

Debian README contains the new URL, we must to be sure to finish this ticket otherwise we must to change the README.

Reference: https://review.jami.net/c/ring-project/+/12774/9/packaging/rules/debian-one-click-install/README.Debian

mentioned in issue #26 (moved)

added CI / CD label

mentioned in issue #28 (closed)

changed title from Rename repos links (but do not break old names!) to Debian: Change rep name from ring to jami

changed the description

added Debian label

changed title from Debian: Change rep name from ring to jami to Debian: repo rename from ring to jami

removed 1 deleted label

unassigned @fpulido

mentioned in issue #54 (moved)

assigned to @sblin

assigned to @mcournoyer

removed milestone %Packaging

added SprintIn progress label

reprepro, the tool we used to generate an apt repository, doesn't seem to support having a mixed distribution (that can be addressed via either 'ring' or 'jami') at the same location. We'll need to investigate other options if we want to pursue that, but IMO it's simpler to keep generating a legacy 'ring' distribution repo along the new 'jami' distribution repo. The configured apt file from the latest packages from both repository would refer to 'jami', effecting the transition.

The legacy distribution repo could be taken down after a reasonable delay.

Pluses:

• simple

Minuses:

• requires to select yet another repo URL; if we use 'nightly' for 'jami', we'd break automatic updates of the users who configured their 'ring' repo manually to point to the nightly URL.

unassigned @sblin

added SprintTo review label and removed SprintIn progress label

closed

added packaging label

mentioned in issue jami-client-qt#1641 (closed)

moved to jami-client-qt#1660 (closed)