Bug#890606: src:kopete: FTBFS against libmediastreamer 2.16

2018-06-21 Thread Félix Sipma
Package: src:kopete
Followup-For: Bug #890606

Have there been any progress on this?

Pino: would the interim solution proposed by Bernhard (temporarily dropping
Jingle support) be acceptable?

Thanks!

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'stable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled


signature.asc
Description: PGP signature


Processed: Re: Bug#890606: src:kopete: FTBFS against libmediastreamer 2.16

2018-05-06 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 help
Bug #890606 [src:kopete] src:kopete: FTBFS against libmediastreamer 2.16
Added tag(s) help.

-- 
890606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#890606: src:kopete: FTBFS against libmediastreamer 2.16

2018-05-06 Thread Bernhard Schmidt
Control: tags -1 help

On Sat, Mar 10, 2018 at 10:51:30AM +0100, Pino Toscano wrote:

Hi Pino,

> (not sure why the bug email did not reach the team ML...)
> 
> In data venerdì 16 febbraio 2018 17:28:12 CET, Bernhard Schmidt ha scritto:
> > src:kopete in unstable FTBFSs against libmediastreamer-dev 1:2.16.1-2
> > currently in experimental.
> > [...]
> > https://bugs.kde.org/show_bug.cgi?id=368340 is an upstream bug about this
> > error which has not seen activity for about a year.
> 
> In comment 8 of that bug, upstream (Pali Rohár) basically asked for help
> about the changed mediastreamer API.  Since nobody followed up on this,
> that explains why the bug has not been fixed so far.
> 
> > We would like to do this transition ASAP and kopete currently is the only
> > hard blocker.
> 
> If so, my suggestion is to help kopete upstream regarding the changed
> mediastreamer API.  Otherwise, with no documentation available, kopete
> upstream is basically stalled on this issue.

Unfortunately I have no idea about the mediastreamer API either (it is
just one of the multiple dependencies of linphone, that's why we package
it). Judging from the way upstream is doing API changes they don't care
about users of their libraries outside of their own stack that much.

I've posted a call for help on the upstream mailinglist at 
http://lists.nongnu.org/archive/html/linphone-developers/2018-05/msg00016.html
but I don't expect much of it.

Would it be an option for you to temporarily drop Jingle support until
this is resolved?

I think the VoIP maintainers team would also like to drop libsrtp0
before Buster, migrating to libsrtp2. Kopete/libjingle will also be a
blocker for this.

Bernhard



Bug#890606: src:kopete: FTBFS against libmediastreamer 2.16

2018-03-10 Thread Pino Toscano
Hi,

(not sure why the bug email did not reach the team ML...)

In data venerdì 16 febbraio 2018 17:28:12 CET, Bernhard Schmidt ha scritto:
> src:kopete in unstable FTBFSs against libmediastreamer-dev 1:2.16.1-2
> currently in experimental.
> [...]
> https://bugs.kde.org/show_bug.cgi?id=368340 is an upstream bug about this
> error which has not seen activity for about a year.

In comment 8 of that bug, upstream (Pali Rohár) basically asked for help
about the changed mediastreamer API.  Since nobody followed up on this,
that explains why the bug has not been fixed so far.

> We would like to do this transition ASAP and kopete currently is the only
> hard blocker.

If so, my suggestion is to help kopete upstream regarding the changed
mediastreamer API.  Otherwise, with no documentation available, kopete
upstream is basically stalled on this issue.

Thanks,
-- 
Pino Toscano

signature.asc
Description: This is a digitally signed message part.