* Re: Package Request: Ring
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
@ 2019-10-29 0:35 ` voidlinux-github
2020-03-05 18:40 ` avoidr
` (23 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: voidlinux-github @ 2019-10-29 0:35 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
New comment by dextruct0r on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-547205327
Comment:
Yes it's a very good app that it's multi arch on some dristro's but it's tricky to manually compile, so if you could add officially to the repo I and some others would be really grateful.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Ring
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
2019-10-29 0:35 ` Package Request: Ring voidlinux-github
@ 2020-03-05 18:40 ` avoidr
2020-09-14 9:29 ` Mirodin
` (22 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: avoidr @ 2020-03-05 18:40 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
New comment by avoidr on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-595383473
Comment:
Here is the code: https://git.jami.net/savoirfairelinux
This repo: https://git.jami.net/savoirfairelinux/ring-project
This repo pulls the other repos as git submodules. But the releases are all only Android, and I have not actually found any code in the release tarballs. And the releases in the individual subrepos are all years old. So I don't know if that even qualifies.
Here is what Arch is doing:
https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/jami-daemon
https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/libjamiclient
https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/jami-gnome
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Ring
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
2019-10-29 0:35 ` Package Request: Ring voidlinux-github
2020-03-05 18:40 ` avoidr
@ 2020-09-14 9:29 ` Mirodin
2021-04-25 9:48 ` autoteelar
` (21 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: Mirodin @ 2020-09-14 9:29 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 225 bytes --]
New comment by Mirodin on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-691937208
Comment:
I too would love to see this on Void, been using it on Android for over a year now.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Ring
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (2 preceding siblings ...)
2020-09-14 9:29 ` Mirodin
@ 2021-04-25 9:48 ` autoteelar
2021-10-10 20:35 ` Package Request: Ring / Jami mika-nl
` (20 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: autoteelar @ 2021-04-25 9:48 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 151 bytes --]
New comment by autoteelar on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-826293712
Comment:
me too
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Ring / Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (3 preceding siblings ...)
2021-04-25 9:48 ` autoteelar
@ 2021-10-10 20:35 ` mika-nl
2021-10-10 20:39 ` mika-nl
` (19 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: mika-nl @ 2021-10-10 20:35 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 167 bytes --]
New comment by mika-nl on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-939548565
Comment:
Love to see Jami in Void
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Ring / Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (4 preceding siblings ...)
2021-10-10 20:35 ` Package Request: Ring / Jami mika-nl
@ 2021-10-10 20:39 ` mika-nl
2021-10-11 18:59 ` Chocimier
` (18 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: mika-nl @ 2021-10-10 20:39 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 280 bytes --]
New comment by mika-nl on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-939548565
Comment:
I would also like to see jami in void.
It's already in most distros
there is a lot of development and I think the p2p idea is the future
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Ring / Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (5 preceding siblings ...)
2021-10-10 20:39 ` mika-nl
@ 2021-10-11 18:59 ` Chocimier
2021-10-13 18:22 ` mika-nl
` (17 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: Chocimier @ 2021-10-11 18:59 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-940364665
Comment:
They do not seem to provide source releases for linux, only [nightly builds](https://jami.net/download-jami-linux/).
All four distros that include it, [Trisquel](https://repology.org/project/jami/versions), [Guix](https://repology.org/project/jami-client-qt/versions), [Mageia, and Arch](https://repology.org/project/jami-daemon/versions) have snapshots.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Ring / Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (6 preceding siblings ...)
2021-10-11 18:59 ` Chocimier
@ 2021-10-13 18:22 ` mika-nl
2021-10-19 1:18 ` jgarte
` (16 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: mika-nl @ 2021-10-13 18:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 192 bytes --]
New comment by mika-nl on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-942593268
Comment:
https://git.jami.net/savoirfairelinux/jami-project
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Ring / Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (7 preceding siblings ...)
2021-10-13 18:22 ` mika-nl
@ 2021-10-19 1:18 ` jgarte
2022-04-15 0:50 ` github-actions
` (15 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: jgarte @ 2021-10-19 1:18 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
New comment by jgarte on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-946288477
Comment:
> I too would love to see this on Void, been using it on Android for over a year now.
How has it worked for you? Any bugs?
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Ring / Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (8 preceding siblings ...)
2021-10-19 1:18 ` jgarte
@ 2022-04-15 0:50 ` github-actions
2022-06-25 1:39 ` Package Request: Jami classabbyamp
` (14 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: github-actions @ 2022-04-15 0:50 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 292 bytes --]
New comment by github-actions[bot] on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1099748858
Comment:
Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (9 preceding siblings ...)
2022-04-15 0:50 ` github-actions
@ 2022-06-25 1:39 ` classabbyamp
2022-06-30 19:22 ` Idesmi
` (13 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: classabbyamp @ 2022-06-25 1:39 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 292 bytes --]
New comment by github-actions[bot] on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1099748858
Comment:
Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (10 preceding siblings ...)
2022-06-25 1:39 ` Package Request: Jami classabbyamp
@ 2022-06-30 19:22 ` Idesmi
2022-06-30 21:49 ` ericonr
` (12 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: Idesmi @ 2022-06-30 19:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 201 bytes --]
New comment by Idesmi on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1171587490
Comment:
I would love to have this, but it's hard to package for me.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (11 preceding siblings ...)
2022-06-30 19:22 ` Idesmi
@ 2022-06-30 21:49 ` ericonr
2023-06-01 6:41 ` chloris-pale-green
` (11 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: ericonr @ 2022-06-30 21:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1171711668
Comment:
I might try packaging this over my holidays, assuming they have started making proper releases. Feel free to ping me for reviewing a PR, if anyone makes one.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (12 preceding siblings ...)
2022-06-30 21:49 ` ericonr
@ 2023-06-01 6:41 ` chloris-pale-green
2023-06-01 10:01 ` chloris-pale-green
` (10 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: chloris-pale-green @ 2023-06-01 6:41 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
New comment by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1571449202
Comment:
Well, it would be about time Void Linux gets something like this in the repos. As [qTox](https://github.com/qTox/qTox) is not actively developed anymore, and getting one's own videoconferencing infrastructure is seriously complicated (compared to chat), we're kinda running out of options for private comms.
I'll give packaging Jami another shot, but expect help requests. My previous attempt was unsuccessful. Let's get it done this time. 😉
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (13 preceding siblings ...)
2023-06-01 6:41 ` chloris-pale-green
@ 2023-06-01 10:01 ` chloris-pale-green
2023-06-01 10:02 ` chloris-pale-green
` (9 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: chloris-pale-green @ 2023-06-01 10:01 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 5189 bytes --]
New comment by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1571738791
Comment:
I've almost successfully packaged `jami-daemon`. The build documentation is quite abysmal. I've ripped off most of the build process from Arch. Dependencies compile successfully, the configure step is successful (except some complaining about `dbus`, which can be disabled, if needed), but the `jami-daemon` itself fails to compile. We don't have `libnatpmp` in the repos, if that's desired.
The compile error seems to be about class member naming:
```
=> jami-daemon-20230601_1: running do_build ...
make all-recursive
make[1]: Entering directory '/builddir/jami-daemon-20230601'
Making all in src
make[2]: Entering directory '/builddir/jami-daemon-20230601/src'
CXX buildinfo.lo
CXX conference.lo
CXX conference_protocol.lo
CXX account_factory.lo
CXX call_factory.lo
CXX preferences.lo
CXX manager.lo
CXX call.lo
CXX gittransport.lo
In file included from /builddir/jami-daemon-20230601/src/media/video/video_input.h:27,
from client/videomanager.h:35,
from preferences.cpp:58:
/builddir/jami-daemon-20230601/src/media/media_stream.h: In constructor 'jami::MediaStream::MediaStream(const std::string&, AVCodecContext*, int64_t)':
/builddir/jami-daemon-20230601/src/media/media_stream.h:115:33: error: 'AVCodecContext' {aka 'struct AVCodecContext'} has no member named 'ch_layout'; did you mean 'channel_layout'?
115 | nbChannels = c->ch_layout.nb_channels;
| ^~~~~~~~~
| channel_layout
/builddir/jami-daemon-20230601/src/media/media_stream.h: In member function 'void jami::MediaStream::update(AVFrame*)':
/builddir/jami-daemon-20230601/src/media/media_stream.h:147:29: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'ch_layout'; did you mean 'channel_layout'?
147 | nbChannels = f->ch_layout.nb_channels;
| ^~~~~~~~~
| channel_layout
In file included from /builddir/jami-daemon-20230601/src/media/media_encoder.h:36,
from /builddir/jami-daemon-20230601/src/media/media_recorder.h:27,
from /builddir/jami-daemon-20230601/src/media/recordable.h:25,
from call.h:32,
from call_factory.h:30,
from call_factory.cpp:23:
/builddir/jami-daemon-20230601/src/media/media_stream.h: In constructor 'jami::MediaStream::MediaStream(const std::string&, AVCodecContext*, int64_t)':
/builddir/jami-daemon-20230601/src/media/media_stream.h:115:33: error: 'AVCodecContext' {aka 'struct AVCodecContext'} has no member named 'ch_layout'; did you mean 'channel_layout'?
115 | nbChannels = c->ch_layout.nb_channels;
| ^~~~~~~~~
| channel_layout
/builddir/jami-daemon-20230601/src/media/media_stream.h: In member function 'void jami::MediaStream::update(AVFrame*)':
/builddir/jami-daemon-20230601/src/media/media_stream.h:147:29: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'ch_layout'; did you mean 'channel_layout'?
147 | nbChannels = f->ch_layout.nb_channels;
| ^~~~~~~~~
| channel_layout
In file included from /builddir/jami-daemon-20230601/src/media/media_encoder.h:36,
from /builddir/jami-daemon-20230601/src/media/media_recorder.h:27,
from /builddir/jami-daemon-20230601/src/media/recordable.h:25,
from call.h:32,
from call_factory.h:30,
from manager.h:35,
from manager.cpp:35:
/builddir/jami-daemon-20230601/src/media/media_stream.h: In constructor 'jami::MediaStream::MediaStream(const std::string&, AVCodecContext*, int64_t)':
/builddir/jami-daemon-20230601/src/media/media_stream.h:115:33: error: 'AVCodecContext' {aka 'struct AVCodecContext'} has no member named 'ch_layout'; did you mean 'channel_layout'?
115 | nbChannels = c->ch_layout.nb_channels;
| ^~~~~~~~~
| channel_layout
/builddir/jami-daemon-20230601/src/media/media_stream.h: In member function 'void jami::MediaStream::update(AVFrame*)':
/builddir/jami-daemon-20230601/src/media/media_stream.h:147:29: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'ch_layout'; did you mean 'channel_layout'?
147 | nbChannels = f->ch_layout.nb_channels;
| ^~~~~~~~~
| channel_layout
```
And so on... Any suggestions? Is is sloppy code or does one of our libraries have different variable names in it than on another distro (`ch_layout` vs `channel_layout`)? We don't need to patch the source files to rename them, right? If that's the case, `sed` would probably do the job.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (14 preceding siblings ...)
2023-06-01 10:01 ` chloris-pale-green
@ 2023-06-01 10:02 ` chloris-pale-green
2023-06-01 14:00 ` chloris-pale-green
` (8 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: chloris-pale-green @ 2023-06-01 10:02 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 5310 bytes --]
New comment by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1571738791
Comment:
I've almost successfully packaged `jami-daemon` (see [this commit](https://github.com/chloris-pale-green/void-packages/commit/e2e1ef07781df3376d0ac3ad15485c36f569caa2)). The build documentation is quite abysmal. I've ripped off most of the build process from Arch. Dependencies compile successfully, the configure step is successful (except some complaining about `dbus`, which can be disabled, if needed), but the `jami-daemon` itself fails to compile. We don't have `libnatpmp` in the repos, if that's desired.
The compile error seems to be about class member naming:
```
=> jami-daemon-20230601_1: running do_build ...
make all-recursive
make[1]: Entering directory '/builddir/jami-daemon-20230601'
Making all in src
make[2]: Entering directory '/builddir/jami-daemon-20230601/src'
CXX buildinfo.lo
CXX conference.lo
CXX conference_protocol.lo
CXX account_factory.lo
CXX call_factory.lo
CXX preferences.lo
CXX manager.lo
CXX call.lo
CXX gittransport.lo
In file included from /builddir/jami-daemon-20230601/src/media/video/video_input.h:27,
from client/videomanager.h:35,
from preferences.cpp:58:
/builddir/jami-daemon-20230601/src/media/media_stream.h: In constructor 'jami::MediaStream::MediaStream(const std::string&, AVCodecContext*, int64_t)':
/builddir/jami-daemon-20230601/src/media/media_stream.h:115:33: error: 'AVCodecContext' {aka 'struct AVCodecContext'} has no member named 'ch_layout'; did you mean 'channel_layout'?
115 | nbChannels = c->ch_layout.nb_channels;
| ^~~~~~~~~
| channel_layout
/builddir/jami-daemon-20230601/src/media/media_stream.h: In member function 'void jami::MediaStream::update(AVFrame*)':
/builddir/jami-daemon-20230601/src/media/media_stream.h:147:29: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'ch_layout'; did you mean 'channel_layout'?
147 | nbChannels = f->ch_layout.nb_channels;
| ^~~~~~~~~
| channel_layout
In file included from /builddir/jami-daemon-20230601/src/media/media_encoder.h:36,
from /builddir/jami-daemon-20230601/src/media/media_recorder.h:27,
from /builddir/jami-daemon-20230601/src/media/recordable.h:25,
from call.h:32,
from call_factory.h:30,
from call_factory.cpp:23:
/builddir/jami-daemon-20230601/src/media/media_stream.h: In constructor 'jami::MediaStream::MediaStream(const std::string&, AVCodecContext*, int64_t)':
/builddir/jami-daemon-20230601/src/media/media_stream.h:115:33: error: 'AVCodecContext' {aka 'struct AVCodecContext'} has no member named 'ch_layout'; did you mean 'channel_layout'?
115 | nbChannels = c->ch_layout.nb_channels;
| ^~~~~~~~~
| channel_layout
/builddir/jami-daemon-20230601/src/media/media_stream.h: In member function 'void jami::MediaStream::update(AVFrame*)':
/builddir/jami-daemon-20230601/src/media/media_stream.h:147:29: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'ch_layout'; did you mean 'channel_layout'?
147 | nbChannels = f->ch_layout.nb_channels;
| ^~~~~~~~~
| channel_layout
In file included from /builddir/jami-daemon-20230601/src/media/media_encoder.h:36,
from /builddir/jami-daemon-20230601/src/media/media_recorder.h:27,
from /builddir/jami-daemon-20230601/src/media/recordable.h:25,
from call.h:32,
from call_factory.h:30,
from manager.h:35,
from manager.cpp:35:
/builddir/jami-daemon-20230601/src/media/media_stream.h: In constructor 'jami::MediaStream::MediaStream(const std::string&, AVCodecContext*, int64_t)':
/builddir/jami-daemon-20230601/src/media/media_stream.h:115:33: error: 'AVCodecContext' {aka 'struct AVCodecContext'} has no member named 'ch_layout'; did you mean 'channel_layout'?
115 | nbChannels = c->ch_layout.nb_channels;
| ^~~~~~~~~
| channel_layout
/builddir/jami-daemon-20230601/src/media/media_stream.h: In member function 'void jami::MediaStream::update(AVFrame*)':
/builddir/jami-daemon-20230601/src/media/media_stream.h:147:29: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'ch_layout'; did you mean 'channel_layout'?
147 | nbChannels = f->ch_layout.nb_channels;
| ^~~~~~~~~
| channel_layout
```
And so on... Any suggestions? Is is sloppy code or does one of our libraries have different variable names in it than on another distro (`ch_layout` vs `channel_layout`)? We don't need to patch the source files to rename them, right? If that's the case, `sed` would probably do the job.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (15 preceding siblings ...)
2023-06-01 10:02 ` chloris-pale-green
@ 2023-06-01 14:00 ` chloris-pale-green
2023-06-01 14:05 ` chloris-pale-green
` (7 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: chloris-pale-green @ 2023-06-01 14:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
New comment by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1572113459
Comment:
Renaming `ch_layout` to `channel_layout` in the code does not work. There seem to be different versions of the `ffmpeg` library with different APIs.
We currently have version 4.4 with [this API](https://ffmpeg.org/doxygen/4.4/structAVCodecContext.html). Struct `AVCodecContext` has a field `uint64_t channel_layout`.
[The `trunk` version](https://ffmpeg.org/doxygen/trunk/structAVCodecContext.html) has another kind of a field: `AVChannelLayout ch_layout`, which seems to be what the Jami code expects. It seems to first appear in `ffmpeg` 5.1. Perhaps an older version of Jami would build ...
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (16 preceding siblings ...)
2023-06-01 14:00 ` chloris-pale-green
@ 2023-06-01 14:05 ` chloris-pale-green
2023-06-01 14:22 ` chloris-pale-green
` (6 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: chloris-pale-green @ 2023-06-01 14:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
New comment by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1572113459
Comment:
Renaming `ch_layout` to `channel_layout` in the code does not work. There seem to be different versions of the `ffmpeg` library with different APIs.
We currently have version 4.4 with [this API](https://ffmpeg.org/doxygen/4.4/structAVCodecContext.html). Struct `AVCodecContext` has a field `uint64_t channel_layout`.
[The `trunk` version](https://ffmpeg.org/doxygen/trunk/structAVCodecContext.html) has another kind of a field: `AVChannelLayout ch_layout`, which seems to be what the Jami code expects. It seems to first appear in `ffmpeg` 5.1. Perhaps an older version of Jami would build ...
In addition, they have switched to `sd-dbus`, which we don't have. Compiling without `dbus` support.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (17 preceding siblings ...)
2023-06-01 14:05 ` chloris-pale-green
@ 2023-06-01 14:22 ` chloris-pale-green
2023-06-01 14:22 ` chloris-pale-green
` (5 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: chloris-pale-green @ 2023-06-01 14:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
New comment by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1572113459
Comment:
Renaming `ch_layout` to `channel_layout` in the code does not work. There seem to be different versions of the `ffmpeg` library with different APIs.
We currently have version 4.4 with [this API](https://ffmpeg.org/doxygen/4.4/structAVCodecContext.html). Struct `AVCodecContext` has a field `uint64_t channel_layout`.
[The `trunk` version](https://ffmpeg.org/doxygen/trunk/structAVCodecContext.html) has another kind of a field: `AVChannelLayout ch_layout`, which seems to be what the Jami code expects. It seems to first appear in `ffmpeg` 5.1. Perhaps an older version of Jami would build ...
In addition, they have switched to `sd-dbus`, which we don't have. Compiling without `dbus` support.
EDIT: compilation proceeds with a pre-FFmpeg 6 commit of the `jami-daemon`, but it chokes on a header, belonging to [RESTinio](https://github.com/Stiffstream/restinio), which we don't have in our repos.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (18 preceding siblings ...)
2023-06-01 14:22 ` chloris-pale-green
@ 2023-06-01 14:22 ` chloris-pale-green
2023-06-01 14:22 ` chloris-pale-green
` (4 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: chloris-pale-green @ 2023-06-01 14:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
New comment by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1572113459
Comment:
Renaming `ch_layout` to `channel_layout` in the code does not work. There seem to be different versions of the `ffmpeg` library with different APIs.
We currently have version 4.4 with [this API](https://ffmpeg.org/doxygen/4.4/structAVCodecContext.html). Struct `AVCodecContext` has a field `uint64_t channel_layout`.
[The `trunk` version](https://ffmpeg.org/doxygen/trunk/structAVCodecContext.html) has another kind of a field: `AVChannelLayout ch_layout`, which seems to be what the Jami code expects. It seems to first appear in `ffmpeg` 5.1. Perhaps an older version of Jami would build ...
In addition, they have switched to `sd-dbus`, which we don't have. Compiling without `dbus` support.
EDIT: compilation proceeds with a pre-FFmpeg 6 commit of `jami-daemon`, but it chokes on a header, belonging to [RESTinio](https://github.com/Stiffstream/restinio), which we don't have in our repos.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (19 preceding siblings ...)
2023-06-01 14:22 ` chloris-pale-green
@ 2023-06-01 14:22 ` chloris-pale-green
2023-06-01 15:00 ` chloris-pale-green
` (3 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: chloris-pale-green @ 2023-06-01 14:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
New comment by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1572113459
Comment:
Renaming `ch_layout` to `channel_layout` in the code does not work. There seem to be different versions of the `ffmpeg` library with different APIs.
We currently have version 4.4 with [this API](https://ffmpeg.org/doxygen/4.4/structAVCodecContext.html). Struct `AVCodecContext` has a field `uint64_t channel_layout`.
[The `trunk` version](https://ffmpeg.org/doxygen/trunk/structAVCodecContext.html) has another kind of a field: `AVChannelLayout ch_layout`, which seems to be what the Jami code expects. It seems to first appear in `ffmpeg` 5.1. Perhaps an older version of Jami would build ...
In addition, they have switched to `sd-dbus`, which we don't have. Compiling without `dbus` support.
EDIT: compilation proceeds with a pre-FFmpeg 6 commit of `jami-daemon`, but it chokes on an inclusion of a header, belonging to [RESTinio](https://github.com/Stiffstream/restinio), which we don't have in our repos.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (20 preceding siblings ...)
2023-06-01 14:22 ` chloris-pale-green
@ 2023-06-01 15:00 ` chloris-pale-green
2023-08-26 14:14 ` HanoJing
` (2 subsequent siblings)
24 siblings, 0 replies; 28+ messages in thread
From: chloris-pale-green @ 2023-06-01 15:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
New comment by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1572113459
Comment:
Renaming `ch_layout` to `channel_layout` in the code does not work. There seem to be different versions of the `ffmpeg` library with different APIs.
We currently have version 4.4 with [this API](https://ffmpeg.org/doxygen/4.4/structAVCodecContext.html). Struct `AVCodecContext` has a field `uint64_t channel_layout`.
[The `trunk` version](https://ffmpeg.org/doxygen/trunk/structAVCodecContext.html) has another kind of a field: `AVChannelLayout ch_layout`, which seems to be what the Jami code expects. It seems to first appear in `ffmpeg` 5.1. Perhaps an older version of Jami would build ...
In addition, they have switched to `sd-dbus`, which we don't have. Compiling without `dbus` support.
EDIT: compilation proceeds with a pre-FFmpeg 6 commit of `jami-daemon`, but it chokes on an inclusion of a header, belonging to [RESTinio](https://github.com/Stiffstream/restinio), which we don't have in our repos.
EDIT2: [RESTinio packaged](https://github.com/chloris-pale-green/void-packages/commit/540c4cd4327eeb34c032ee543344fd981fd4a3de), but I have no idea how to use it without pushing it to Void repos first.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (21 preceding siblings ...)
2023-06-01 15:00 ` chloris-pale-green
@ 2023-08-26 14:14 ` HanoJing
2023-08-30 18:14 ` Chocimier
2024-06-14 13:39 ` [ISSUE] [CLOSED] " ahesford
24 siblings, 0 replies; 28+ messages in thread
From: HanoJing @ 2023-08-26 14:14 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
New comment by HanoJing on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1694350204
Comment:
Hey all, I have written a guide on how to build Jami on Void Linux:
https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1327
It takes like 20-30 minutes to compile on my machine, but I hope this guide helps some of you if you have enough processing power available and don't want to wait till it's packaged.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (22 preceding siblings ...)
2023-08-26 14:14 ` HanoJing
@ 2023-08-30 18:14 ` Chocimier
2024-06-14 13:39 ` [ISSUE] [CLOSED] " ahesford
24 siblings, 0 replies; 28+ messages in thread
From: Chocimier @ 2023-08-30 18:14 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 260 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1699615743
Comment:
jami-client-qt got tagged as stable few times by now, and it contains server part. I would be fine with merging it.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: [ISSUE] [CLOSED] Package Request: Jami
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
` (23 preceding siblings ...)
2023-08-30 18:14 ` Chocimier
@ 2024-06-14 13:39 ` ahesford
24 siblings, 0 replies; 28+ messages in thread
From: ahesford @ 2024-06-14 13:39 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
Closed issue by Seeder101 on void-packages repository
https://github.com/void-linux/void-packages/issues/4420
Description:
Ring P2P Communication Tool.
it's an open source gnu project software. geared toward decentralization with P2P chat and voice system.
you can take a look at the project page : https://jami.net
Thank you in advance.
^ permalink raw reply [flat|nested] 28+ messages in thread