Debian: official distribution repository package

• Analize Jami and Debian Versions and releases
• Define strategy
• Contact developer to work together

Related: jami-packaging#8 (moved)

assigned to @abandali

Analysis

Debian Stable (10, Buster)

• Initially released as version 10 on July 6th, 2019
• Buster Freeze Timeline and Policy
  • 2019-01-12 - Transition freeze
  • 2019-02-12 - Soft-freeze
  • 2019-03-12 - Full-freeze
• Jami 20190215.1.f152c98~ds1-1

It means the actual maintainer do his job almost perfectly.

Debian Testing (Bullseye)

• Bullseye Freeze Timeline and Policy (DRAF)
  • No defined date for now
• Jami 20190215.1.f152c98~ds1-1 (same as Buster)

It means we can provide a most recent version of Jami to Debian Testing users (Debian testing is often used as workstation distribution)

Debian Unstable (Sid)

• Jami 20190215.1.f152c98~ds1-1 (same as Buster)

It means no any proactive work, for now could be a good practice to publish once per month, in this way this packages will be moved to testing more frequently.

changed title from Debian official repository package to Debian: official distribution repository package

added Debian in jami-packaging label

changed the description

mentioned in issue jami-packaging#18 (moved)

added Community in jami-packaging label

added 1 deleted label

This is the maintainer answer:

Hellom

If the new version of ring builds fine without any changes, just let
me know and I will upload it.

Otherwise, please send me patches to be applied on my packaging.

I keep my packaging updated here:
 - https://salsa.debian.org/pkg-voip-team/ring/tree/master/debian

You can clone the repo, but not modify it.

Feel free to send me patches (by email) that modify the debian/ folder
so that we can build the newer versions of ring.

BTW, I speak french if you prefer that.

Cheers,


--
Alexandre Viau
alexandre@alexandreviau.net

made the issue confidential

unassigned @fpulido

removed 1 deleted label

I Answer Alexandre to explain I'll go in-house for a client then makes no sense to be in charge, I told him we are looking for some one to take care about the technical community tasks.

mentioned in issue jami-packaging#46 (closed)

mentioned in issue jami-packaging#48 (closed)

assigned to @abandali

My patch for bumping Debian unstable's opendht to latest release was merged in the weekend. It also added CONFIGURE_FLAGS useful for recent versions of Jami.

I'd also already sent a patch fixing build of the newer jami_20191214.1.07edb5e on unstable, but it might need some dependency list tweaks to ensure it builds in a clean environment (e.g. using git-pbuilder).

made the issue visible to everyone

New update: OpenDHT in unstable is now on latest upstream release, and Jami in unstable has been bumped to a more recent version, mentioned above, and both seem to be building successfully at least on a good number of architectures.

The current plan I think is to wait for these two updates to reach from unstable to testing, then try bumping Jami to latest upstream release and look into adding these to backports and potentially proposed-updates (meaning that it may be available to users in a future point-release of the current stable).

closed

added packaging label

moved from jami-packaging#12 (moved)