Hi Sunil,
Sorry for jumping in but I recently answered on the same topic:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760485#54
And here I had attached the dependencies for all the packages
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760485#74 and as I did it half a year ago, half of it had probably already changed...
FastTrack sounds good. The current pace is a release every 2-3 months, if
the new versions can go there directly that sounds like it will solve the problem. But, of course, we want to speed up this process.
You said: "Once the packages have stabilized enough (over the months/years) they can move into unstable/testing/stable. "
Looking at the past 5-6 years, there is no such thing as "stabilized enough
", I can give you many examples ... and there is one coming in August ...
PlanB will be dropped off from chrome. So this means whatever version you
have of jitsi-meet, it will stop working in August and everyone needs to
update to the latest stable that we even haven't started working on yet and probably will be out a month or so earlier.
So for the past 5-6 years, this is how things move, every browser updates
at a 6-week pace, and we basically follow it. So we need to be pushing
releases every 6 weeks and someone needs to dedicate be working on that to update the repositories with the new version and work on adding the new dependencies to the official repos ...
Thanks for the interest
damencho
On Tue, Apr 27, 2021 at 11:49 AM Sunil Mohan Adapa <
sunil@medhas.org> wrote:
On 26/04/21 12:03 am, Ingo Bauersachs wrote:
[...]
I'm a committer in Jitsi and lurking around here. The idea to get
Jitsi Meet into Debian is IMO very ambitious. I'm wondering how you
intend to keep the packages up-to-date once they entered a stable
release? WebRTC is such a fast moving technology and having a year
old Videobridge is likely going to be broken/not working anymore.
I am only vaguely aware of the issue with Jitsi Meet doing catch up with WebRTC standard due to something I read earlier. I hope Jitsi
Videobridge does not suffer the same issue. Or do Meet and Videobridge
have strong version dependencies?
One idea is to maintain the fast moving packages in Debian
fasttrack[1][2]. Once the packages have stabilized enough (over the months/years) they can move into unstable/testing/stable. In FreedomBox,
we have made the decision to make selected packages from fasttrack
available to our end users (this will be backed by user interface to set
user expectations, daily automatic software updates, scheduled snapshots
and backups).
Also, some packages already in Debian (and some in Jitsi) are old and
would need updating.
I will request/assist the maintainers for newer version of these packages.
For others, packaging the version used currently
in Jitsi is somewhat questionable: the used version of Smack for
example is a fork, upstream is at 4.4, but unfortunately, they don't
follow SemVer and updating is a major pain. The same often goes with BouncyCastle.
In this case, it may become appropriate to maintain multiple versions of
the package: smack-4.4, smack-4.5, etc. In general, this is undesirable
due to increased bug fixing and security effort. We should try to avoid
it especially if no other packages depend on the library.
I'm currently working on building packages for Jitsi
Desktop again, but I'm not considering submitting them to Debian,
there are just too many floating dependencies.
It would certainly be nice to have it in Debian. Please see if it is at
least suitable for fasttrack.
I really don't want to discourage you but hoping to make you aware of
the potential (and upcoming) issues.
I understand. I appreciate the information you have provided as it would avoid surprises later.
Having a robust, mature and feature rich video conferencing in
FreedomBox is critical. It has been voted the number one priority in
this year's roadmap. I have several months of time set aside to work on
Jitsi and I feel prepared to take on the challenge :)
I'm not sure if you're active in
Jitsi's discussions forums (I'm not), but in any case, Damencho or I
would certainly help you need patches applied upstream, you can ping
me in issues/PRs with @ibauersachs.
I just subscribed to the Developers category in the forums. I will
publish packaging updates there as well.
Thank you for the offer, I will be sure you ping you in my merge requests.
FYI, the package jain-sip-ri-oss-only is just Jain SIP/jsip [1], but without the non open-source files (src/javax/*). The Maven packing is
in the Jitsi fork at [2]. The removed files are in the Debian package libsdp-api-java and libsip-api-java (as a clean-room
reimplementation). java-sdp-nist-bridge is used to reconnect the
deleted sources and libsdp-api-java. Jain-sip, without the
repackaging, was the original reason why Jitsi Desktop never made it
into Debian (i.e. past the FTP masters) and subsequent efforts were
then dropped.
I see. Good to know. I will package these bits accordingly.
Links:
1) https://fasttrack.debian.net/
2) https://wiki.debian.org/FastTrack
Thanks,
--
Sunil
<div dir="ltr">Hi Sunil,<div><br></div><div>Sorry for jumping in but I recently answered on the same topic:</div><div><a href="
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760485#54">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760485#54</a><br>
</div><div>And here I had attached the dependencies for all the packages <a href="
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760485#74">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760485#74</a> and as I did it half a year ago, half of it had
probably already changed... <br></div><div><br></div><div>FastTrack sounds good. The current pace is a release every 2-3 months, if the new versions can go there directly that sounds like it will solve the problem. But, of course, we want to speed up
this process. </div><div><br></div><div>You said: "Once the packages have stabilized enough (over the months/years) they can move into unstable/testing/stable. " </div><div>Looking at the past 5-6 years, there is no such thing as "
stabilized enough ", I can give you many examples ... and there is one coming in August ... PlanB will be dropped off from chrome. So this means whatever version you have of jitsi-meet, it will stop working in August and everyone needs to update to
the latest stable that we even haven't started working on yet and probably will be out a month or so earlier. </div><div>So for the past 5-6 years, this is how things move, every browser updates at a 6-week pace, and we basically follow it. So we
need to be pushing releases every 6 weeks and someone needs to dedicate be working on that to update the repositories with the new version and work on adding the new dependencies to the official repos ... </div><div><br></div><div>Thanks for the
interest</div><div>damencho</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 27, 2021 at 11:49 AM Sunil Mohan Adapa <<a href="mailto:
sunil@medhas.org">
sunil@medhas.org</a>> wrote:<br></div><
blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 26/04/21 12:03 am, Ingo Bauersachs wrote:<br>
[...]<br>
> <br>
> I'm a committer in Jitsi and lurking around here. The idea to get<br> > Jitsi Meet into Debian is IMO very ambitious. I'm wondering how you<br>
> intend to keep the packages up-to-date once they entered a stable<br>
> release? WebRTC is such a fast moving technology and having a year<br> > old Videobridge is likely going to be broken/not working anymore.<br>
I am only vaguely aware of the issue with Jitsi Meet doing catch up with<br> WebRTC standard due to something I read earlier. I hope Jitsi<br>
Videobridge does not suffer the same issue. Or do Meet and Videobridge<br>
have strong version dependencies?<br>
One idea is to maintain the fast moving packages in Debian<br>
fasttrack[1][2]. Once the packages have stabilized enough (over the<br> months/years) they can move into unstable/testing/stable. In FreedomBox,<br>
we have made the decision to make selected packages from fasttrack<br> available to our end users (this will be backed by user interface to set<br> user expectations, daily automatic software updates, scheduled snapshots<br> and backups).<br>
> <br>
> Also, some packages already in Debian (and some in Jitsi) are old and<br> > would need updating.<br>
I will request/assist the maintainers for newer version of these packages.<br>
> For others, packaging the version used currently<br>
> in Jitsi is somewhat questionable: the used version of Smack for<br>
> example is a fork, upstream is at 4.4, but unfortunately, they don't<br>
> follow SemVer and updating is a major pain. The same often goes with<br> > BouncyCastle.<br>
In this case, it may become appropriate to maintain multiple versions of<br> the package: smack-4.4, smack-4.5, etc. In general, this is undesirable<br>
due to increased bug fixing and security effort. We should try to avoid<br>
it especially if no other packages depend on the library.<br>
> I'm currently working on building packages for Jitsi<br>
> Desktop again, but I'm not considering submitting them to Debian,<br> > there are just too many floating dependencies.<br>
It would certainly be nice to have it in Debian. Please see if it is at<br> least suitable for fasttrack.<br>
> <br>
> I really don't want to discourage you but hoping to make you aware of<br>
> the potential (and upcoming) issues. <br>
I understand. I appreciate the information you have provided as it would<br> avoid surprises later.<br>
Having a robust, mature and feature rich video conferencing in<br>
FreedomBox is critical. It has been voted the number one priority in<br>
this year's roadmap. I have several months of time set aside to work on<br> Jitsi and I feel prepared to take on the challenge :)<br>
> I'm not sure if you're active in<br>
> Jitsi's discussions forums (I'm not), but in any case, Damencho or I<br>
> would certainly help you need patches applied upstream, you can ping<br> > me in issues/PRs with @ibauersachs.<br>
I just subscribed to the Developers category in the forums. I will<br>
publish packaging updates there as well.<br>
Thank you for the offer, I will be sure you ping you in my merge requests.<br>
> <br>
> FYI, the package jain-sip-ri-oss-only is just Jain SIP/jsip [1], but<br> > without the non open-source files (src/javax/*). The Maven packing is<br> > in the Jitsi fork at [2]. The removed files are in the Debian package<br> > libsdp-api-java and libsip-api-java (as a clean-room<br>
> reimplementation). java-sdp-nist-bridge is used to reconnect the<br>
> deleted sources and libsdp-api-java. Jain-sip, without the<br>
> repackaging, was the original reason why Jitsi Desktop never made it<br> > into Debian (i.e. past the FTP masters) and subsequent efforts were<br> > then dropped.<br>
I see. Good to know. I will package these bits accordingly.<br>
Links:<br>
1) <a href="
https://fasttrack.debian.net/" rel="noreferrer" target="_blank">
https://fasttrack.debian.net/</a><br>
2) <a href="
https://wiki.debian.org/FastTrack" rel="noreferrer" target="_blank">
https://wiki.debian.org/FastTrack</a><br>
Thanks,<br>
-- <br>
Sunil<br>
</blockquote></div>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)