Dear all,
I'm trying to make a telepathy-based IRC client to show every
channel's description. For that, I'm using RoomInfo.get_description().
However, that method always returns null. I'm not sure why. I've
checked other information in RoomInfo, and there are other properties
that seem
The "Ages Later" release.
tarball:
https://telepathy.freedesktop.org/releases/telepathy-glib/telepathy-glib-0.24.2.tar.gz
signature:
https://telepathy.freedesktop.org/releases/telepathy-glib/telepathy-glib-0.24.2.tar.gz.asc
git: https://cgit.freedesktop.org/telepathy/tele
Daniel-Constantin Mierla
- Daniel Pocock
- Guus der Kinderen
_______
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
tarball:
http://telepathy.freedesktop.org/releases/telepathy-idle/telepathy-idle-0.2.2.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-idle/telepathy-idle-0.2.2.tar.gz.asc
git: https://gitlab.freedesktop.org/telepathy/telepathy-idle
It seems that I accidentally merged
telepathy-idle 0.2.1 release.
tarball:
https://telepathy.freedesktop.org/releases/telepathy-idle/telepathy-idle-0.2.1.tar.gz
signature:
https://telepathy.freedesktop.org/releases/telepathy-idle/telepathy-idle-0.2.1.tar.gz.asc
git: https://gitlab.freedesktop.org/telepathy/telepathy-idle
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
The "leave no space" release.
tarball:
http://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-5.16.6.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-5.16.6.tar.gz.asc
The "three plus one" release.
tarball:
http://telepathy.freedesktop.org/releases/telepathy-spec/telepathy-spec-0.27.4.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-spec/telepathy-spec-0.27.4.tar.gz.asc
git: http://cgit.freedesktop.org/telepathy/telepathy-spe
The "Still moving" release.
tarball:
https://telepathy.freedesktop.org/releases/telepathy-qt/telepathy-qt-0.9.8.tar.gz
signature:
https://telepathy.freedesktop.org/releases/telepathy-qt/telepathy-qt-0.9.8.tar.gz.asc
git: http://cgit.freedesktop.org/telepathy/telepathy-qt
Dependencies
The "magic number three" release.
tarball:
http://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-5.16.5.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-5.16.5.tar.gz.asc
Hello!
I'm looking for the list of supported XMPP XEPs by Empathy. All I
could find was this
https://telepathy.freedesktop.org/components/telepathy-gabble/ webpage
with a warning "This list is incomplete and quite possibly out of
date"
So where can I find the complete up-to-date li
Folks,
Is there a current release manager for telepathy and/or telepathy-gabble?
Back on November 30th, 2018, a critical build fix to resolves failure to
build from source for telepathy-gabble 0.18.4 was made.
I would like to request that whomever is capable of doing so release
telepathy
On Thu, 2018-08-23 at 12:40 +0200, Johannes Winter wrote:
> Hello everybody,
>
> I'm running empathy with telepathy-rakia on latest debian sid and
> like
> to use my fritzbox router for making SIP calls.
>
> Calling works, but sound quality is far beyond acceptable, onl
Hello everybody,
I'm running empathy with telepathy-rakia on latest debian sid and like
to use my fritzbox router for making SIP calls.
Calling works, but sound quality is far beyond acceptable, only grunting
sounds arrive at the other side.
Looking at the system messages they show these maybe
Hi,
I am Rahul, contributing to Sugar Labs.
I am porting our code from telepathy-python to TelepathyGLib (PyGI).
(1) While porting, I could not figure out how to specify the
`ready_handler` and `error_handler` functions in TelepathyGLib.Channel.
Eg: We are using it here -
https://github.com/Pro
On Tue, May 15, 2018 at 03:36:36PM +0200, Emilio Pozuelo Monfort wrote:
> On 15/05/18 14:38, Rahul Bothra wrote:
> > Hi,
> >
> > We (Sugar), are using telepathy for our Python 2 version. We are
> > porting to Python 3.
> >
> > Is a Python 3.x telepathy
Hi,
Thank you, but I didn't quite understand what you proposed.
Currently, our code is written in Python 2 (and PyGTK+ 3) and we are using
the telepathy python library. We are porting to Python 3, and I am looking
for a Python 3 version of Telepathy (preferably, maintained
like to ask, should it work also, and I have something wrong here,
or it is really the only piece od GOA which is not working with 2step
verification?
--
Pozdrawiam, Jakub.
Milion osób dziennie pobiera Firefoksa... pobierz i Ty! firefox.pl
___
telepathy
Hi,
We (Sugar), are using telepathy for our Python 2 version. We are porting to
Python 3.
Is a Python 3.x telepathy build available or are there any plans to release
the same ?
Thanks and Regards
Rahul
___
telepathy mailing list
telepathy
Hello
>
> Please, go ahead. I can also make releases, but I have a lot in my
> backlog right now. The instructions should be straightforward.
They look pretty straight forward... Thank you for updating the wiki.
> Please, also push the changes on the github telepathy-idle
ase all project presented at freedesktop.org
> via freedesktop.org at the first place and via github.com as the
> second place. I can help with both, but I develop only Qt side of
> things. Maybe there is something like "maintainer-upload-release"
> target in telepathy-idle? We h
ngs. Maybe there is something like "maintainer-upload-release"
target in telepathy-idle? We have such one in telepathy-qt.
On Sat, Nov 4, 2017 at 12:31 AM, Diane Trout <di...@ghic.org> wrote:
> On Fri, 2017-11-03 at 17:18 -0400, Olivier Crête wrote:
>> Hi,
>>
On Fri, 2017-11-03 at 17:18 -0400, Olivier Crête wrote:
> Hi,
>
> I believe the most active maintenance of Telepathy is now at
>
> https://github.com/TelepathyIM
>
> Olivier
I believe so too...
Should we have new releases go through freedesktop.org? or just make
github r
Hi,
I believe the most active maintenance of Telepathy is now at
https://github.com/TelepathyIM
Olivier
On Fri, 2017-11-03 at 10:35 -0700, Diane Trout wrote:
> Hi,
>
> Anyone still around who can handle doing releases?
>
> There's a request for a new release of telepathy-
Hi,
Anyone still around who can handle doing releases?
There's a request for a new release of telepathy-idle
https://bugs.freedesktop.org/show_bug.cgi?id=94189
And Polari is actually maintained and reasonably well liked.
(Also Hi team members, I'm starting to have time again. In case you
t;> On 07/12/16 16:22, Gustavo Boiko wrote:
>> > Hi Daniel
>> >
>> > On Sat, Nov 19, 2016 at 12:54 PM, Daniel Pocock <dan...@pocock.pro
>> <mailto:dan...@pocock.pro>
>> > <mailto:dan...@pocock.pro <mailto:dan...@pocock.pro>>> wro
; On Sat, Nov 19, 2016 at 12:54 PM, Daniel Pocock <dan...@pocock.pro
> <mailto:dan...@pocock.pro>
> > <mailto:dan...@pocock.pro <mailto:dan...@pocock.pro>>> wrote:
> >
> >
> > Debian has telepathy-qt for both qt4 and qt5:
>
Hi
On Wed, Dec 7, 2016 at 1:33 PM, Daniel Pocock <dan...@pocock.pro> wrote:
>
>
> On 07/12/16 16:22, Gustavo Boiko wrote:
> > Hi Daniel
> >
> > On Sat, Nov 19, 2016 at 12:54 PM, Daniel Pocock <dan...@pocock.pro
> > <mailto:dan...@pocock.pro>
On 07/12/16 16:22, Gustavo Boiko wrote:
> Hi Daniel
>
> On Sat, Nov 19, 2016 at 12:54 PM, Daniel Pocock <dan...@pocock.pro
> <mailto:dan...@pocock.pro>> wrote:
>
>
> Debian has telepathy-qt for both qt4 and qt5:
>
> https://packages.qa.debi
Debian has telepathy-qt for both qt4 and qt5:
https://packages.qa.debian.org/t/telepathy-qt.html
So far, we've been building and testing telepathy-resiprocate with qt4 only
I've just updated the resiprocate 1.11.0~alpha1 to Debian, which adds a
telepathy-resiprocate.deb for the first time
On 18/11/16 09:59, George Kiagiadakis wrote:
> On 11/18/2016 10:27 AM, Daniel Pocock wrote:
>>
>> Debian unstable and testing currently have TelepathyQt 0.9.6.1:
>>
>> https://packages.qa.debian.org/t/telepathy-qt.html
>>
>> I'm going to make a resiprocate
Debian unstable and testing currently have TelepathyQt 0.9.6.1:
https://packages.qa.debian.org/t/telepathy-qt.html
I'm going to make a resiprocate 1.11 release depending on that specific
version for the telepathy-resiprocate connection manager. That will
then be uploaded to Debian as a package
speakers and participants to discuss the selection
process and other aspects of FOSDEM on the Free-RTC mailing list:
https://lists.fsfe.org/mailman/listinfo/free-rtc
___
telepathy mailing list
telepathy@lists.freedesktop.org
https
in Klapetek | KDE Developer
_______
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
_______
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
ould be steering a reviewer into
accepting code. You're probably right, though, the more I think about it the
more it seems like a non-issue; the Telepathy committers aren't me ;)
> > * Poor commit messages are understood as valid grounds to reject a
> >patch
>
> It is equally a
nderstood as valid grounds to reject a
>patch
It is equally a valid point to reject a commit.
> * editing a patch is easier than rewriting branch history
No. Rewriting a branch is easier, if you use a proper tool (git rebase
--interactive; git add --patch at the very least).
> * Ther
branch history
* There's no argument over git merge vs git rebase, over a commit log
full of merge commits or rewriting history
Particularly with a project with as many components as Telepathy, I feel
like GitHub issues would be a definite step backward.
I'd also recommend BZ over Phabricator,
fore, the point is valid, so the new plan now is to finish
> > Telepathy 1.0 as soon as possible and then carry on with a clean spec
> > and codebase.
> >
>
> Has any target date been set for this?
>
> Is it intended to be part of the next Debian release? If so, t
ves contains only the
>> > tree snapshot from a tagged commit.
>> > 2) The archive directory name is project name + tag name. For
>> > TelepathyQt we have archive "telepathy-qt-0.9.7.tar.gz" with directory
>> > "telepathy-qt-telepathy-qt-0.9.7".
>> &
On 30/10/16 17:59, George Kiagiadakis wrote:
> Therefore, the point is valid, so the new plan now is to finish
> Telepathy 1.0 as soon as possible and then carry on with a clean spec
> and codebase.
>
Has any target date been set for this?
Is it intended to be part of the next De
se in some special way. Namely, we generate
> > documentation for release tarballs. Github archives contains only the
> > tree snapshot from a tagged commit.
> > 2) The archive directory name is project name + tag name. For
> > TelepathyQt we have archive "telepathy-qt-0.9.7.t
pecial way. Namely, we generate
> documentation for release tarballs. Github archives contains only the
> tree snapshot from a tagged commit.
> 2) The archive directory name is project name + tag name. For
> TelepathyQt we have archive "telepathy-qt-0.9.7.tar.gz" with directory
s contains only the tree
snapshot from a tagged commit.
2) The archive directory name is project name + tag name. For TelepathyQt
we have archive "telepathy-qt-0.9.7.tar.gz" with directory
"telepathy-qt-telepathy-qt-0.9.7".
I think we should use https://telepathy.freedesktop.org/re
ested in project news.
>
> Telepathy 1.0
> =
>
> After some discussion with ramcq, Kaffeine suggested that we should
> proceed with releasing telepathy 1.0 before introducing new features, as
> it is easier at this point to merge the 'next' branches that were le
Hi all,
There was a discussion on IRC on Friday about our short-term plans. I
will summarize it here for the archive and for anyone else who is
interested in project news.
Telepathy 1.0
=
After some discussion with ramcq, Kaffeine suggested that we should
proceed with releasing
https://lists.fsfe.org/mailman/listinfo/free-rtc
The dev-room administration team:
Saúl Ibarra Corretgé <sag...@gmail.com>
Iain R. Learmonth <i...@debian.org>
Ralph Meijer <ral...@ik.nu>
Daniel-Constantin Mierla <mico...@gmail.com>
Daniel Pocock <dan...@poco
On 14/10/16 15:31, ronald.ev...@l-3com.com wrote:
> /Hello, We are looking for a library that we can build or link into a
> Visual Studio project, that would allow us to send voice over an
> Ethernet link from one Windows PC to another. No other functionality at
> this time. Wou
Hello, We are looking for a library that we can build or link into a Visual
Studio project, that would allow us to send voice over an Ethernet link from
one Windows PC to another. No other functionality at this time. Would
Telepathy be suitable for this? Can you please recommend what
ial' contact
> list (like [1] and [2]), right?
>
> [1]
> https://github.com/TelepathyQt/telepathy-nonsense/blob/master/connection.cc#L499
> [2]
> https://github.com/TelepathyQt/telepathy-morse/blob/master/connection.cpp#L661
>
You're right, there should be an "official" lis
I have just noticed that telepathy-morse actually uses the m_handles as the
'oficial' contact list: it is used to get the contacts in
GetContactListAttributes() and the contacts are added there in the
requestHandles() calling.
[1]
https://github.com/TelepathyQt/telepathy-morse/blob/master
ate...@test.sip5060.net) in the map that shouldn't be a problem, right?
And if so, then you would have another way of getting the 'official'
contact list (like [1] and [2]), right?
[1]
https://github.com/TelepathyQt/telepathy-nonsense/blob/master/connection.cc#L499
[2]
https://github.com/Tele
Morse and Nonsense both returns a handle list.
In case of Nonsense: type of the list is UniqueHandleMap with
operators and the used operator [] will return a new handle for each
new identifier.
https://github.com/TelepathyQt/telepathy-nonsense/blob/master/uniquehandlemap.cc#L32
The identifier
l list of contacts?
> The RequestHandles method do exactly
> one thing: returns valid handle for identifier. Error "Invalid
> Handle" should be returned if the given identifier does not identify a
> valid entity of the given type.
Looking at telepathy-nonsense [1]
On 09/19/2016 08:59 PM, Mateus Bellomo wrote:
> Hello,
>
> I have implemented the requestSubscription() and requestHandles()
> methods at telepathy-resiprocate [1]. I'm using Empathy as a client and
> testing it I noticed that when I try to add a contact in the contact
> l
nts to get know if the typed
> contact is valid and exists. Telepathy have no such API, so Empathy
> has to workaround it via trying to get info about the contact by typed
> identifier, which (usually) triggers handle assignment, or results in
> "InvalidHandle" error.
>
> The thi
Hello,
I have implemented the requestSubscription() and requestHandles() methods
at telepathy-resiprocate [1]. I'm using Empathy as a client and testing it
I noticed that when I try to add a contact in the contact list, in the
window that opens, the method requestHandle() is being called several
Would you consider adding Mozilla's IRC settings to irc-networks.xml?
Here are the settings:
https://wiki.mozilla.org/IRC
And I think this is where the file is currently maintained?
https://git.gnome.org/browse/telepathy-account-widgets/tree/tp-account-widgets/irc-networks.xml
before I can start typing the name of a contact I'm interested
> in.
>
> Regards,
> Piotr Dobrogost
>
> ps.
> If "Instant Messaging" systray applet is not being developed by the
> telepathy team then please point me to the right place.
Sorry, but this is the cas
Hi!
I set "Log to a file" for specific contact for "Contact status
changed" notification yet there are no entries in the file given when
setting this option.
Am I missing something?
Regards,
Piotr Dobrogost
___
telepathy ma
there some bug or request for this feature present?
Regards,
Piotr Dobrogost
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
Dobrogost
ps.
If "Instant Messaging" systray applet is not being developed by the
telepathy team then please point me to the right place.
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
I think it's better if I could look at the source code as you said before.
Just to confirm. the Empathy source is at [1] and telepathy-qt is at [2],
right?
[1] https://github.com/GNOME/empathy
[2] https://cgit.freedesktop.org/telepathy/telepathy-qt
2016-07-25 2:05 GMT-03:00 George Kiagiadakis
> My guess is that telepathy-logger and Empathy try to get the contact's
> name by using the Connection.I.Aliasing interface [2]. Do you implement
> Tp::BaseConnectionAliasingInterface [3] in your CM?
I think so. At [1] I've created the Tp::BaseConnectionAliasingInterface and
at [2] and
On 07/23/2016 11:48 PM, Mateus Bellomo wrote:
> Hello,
>
> I would like to know if there is a page describing the
> addReceivedMessage() telepathy method. I have searched at google but
> didn't find anything, just usage examples at [1], [2], [3] and [4].
I don't think so, th
Hello,
I would like to know if there is a page describing the addReceivedMessage()
telepathy method. I have searched at google but didn't find anything, just
usage examples at [1], [2], [3] and [4].
At [5] there is a Tp::BaseChannelTextTye class reference but there is no
description
nd it's working.
>
> Just one more question: I don't know if this is related to telepathy but
> when I receive a message at Empathy and the chat window is not open, it
> appears a little box at the bottom of the screen with that message. I saw
> at the debug log that a new channel
great...many thanks for all this explanation!
I've changed for the way you said [1] and it's working.
Just one more question: I don't know if this is related to telepathy but
when I receive a message at Empathy and the chat window is not open, it
appears a little box at the bottom of the screen
the "to" header, and since this is a
"message received" method, the "to" is your self contact, not the remote
one. In 1-1 channels, TargetHandle must be the remote contact.
I just had a look at how telepathy-qt implements ensureChannel() and now
I fully understand what tele
Handles [1]. There is no definite answer for the
format of these identifiers in the spec, but telepathy-glib docs [2] do
mention that it should be a SIP URI (so, with the prefix) in the case of
SIP. In the end I think this is your choice. It just needs to be
something that can *uniquely* identify a contact i
and InitiatorID must have the prefix "sip:"
> (e.g. sip:mateusbell...@sip.antisip.com)?
>
> 2016-07-22 2:35 GMT-03:00 George Kiagiadakis <gkia...@tolabaki.gr>:
>
>> On 21.07.2016 22:07, Mateus Bellomo wrote:
>>
>>> Hello,
>>>
>>> I've
;
>> Hello,
>>
>> I've implemented methods to send and receive text message at
>> telepathy-resiprocate but I think I'm mixing the sender/receiver
>> handles. I'm using telepathy-morse [1] as a guide and I would like to
>> know what is the meaning of contactHandle,
On 21.07.2016 22:07, Mateus Bellomo wrote:
Hello,
I've implemented methods to send and receive text message at
telepathy-resiprocate but I think I'm mixing the sender/receiver
handles. I'm using telepathy-morse [1] as a guide and I would like to
know what is the meaning of contactHandle
Hello,
I've implemented methods to send and receive text message at
telepathy-resiprocate but I think I'm mixing the sender/receiver handles.
I'm using telepathy-morse [1] as a guide and I would like to know what is
the meaning of contactHandle, targetHandle and initiatorHandle.
Right now I can
Will anybody from the Telepathy community be at QtCon[1] ?
I've been invited to speak about free real-time communications at the
FSFE Summit[2], which is happening in conjunction with QtCon this year.
Regards,
Daniel
1. https://qtcon.org/
2. https://fsfe.org/community/events/2016/summit
On Mon, Jul 4, 2016 at 9:38 PM, Diane Trout <di...@ghic.org> wrote:
> Do you have kaccounts, signond, and telepathy sign on plugin (I think
I think so:
[piotr@demon ~]$ rpm -qa | grep kaccounts
kaccounts-integration-16.04.2-1.fc24.x86_64
kaccounts-providers-16.04.2-1.fc24.x86_64
[pi
Do you have kaccounts, signond, and telepathy sign on plugin (I think those are
package names, I'm not at computer right now). I think I also has issues with
upgrades, so if the accounts created pre kaccounts they might not have password
saved, also there's a ag-tool command for inspecting
x86_64
ktp-accounts-kcm-16.04.2-1.fc24.x86_64
ktp-desktop-applets-16.04.2-1.fc24.x86_64
Regards,
Piotr Dobrogost
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
> > import gi
> > gi.extend_path('/telepathy-glib/telepathy-glib/',
> > 'TelepathyGLib-0.12')
> > gi.require_version('TelepathyGLib', '0.12')
> >
> > To try and grab the recently built typelib instead of any one
> > potentially already installed.
On 01.07.2016 08:49, Diane Trout wrote:
Hi,
A long time ago I had briefly tried to use telepathy-glib from python
and gave up because it kept segfaulting.
I've been wondering how hard it would be to add tests to telepathy-glib
to verify that the gobject introspection bindings are working
Hi Mateus,
For message *receiving* you don't have to implement a method in
interface (because method is something to be called by a telepathy
client application). Instead, client listens for messageReceived
signal [1], which you should emit for every incoming message.
[1]
https
] https://telepathy.freedesktop.org/spec/Channel_Type_Text.html
[3]
https://github.com/TelepathyQt/telepathy-morse/blob/master/textchannel.cpp
[4]
https://github.com/TelepathyQt/telepathy-nonsense/blob/master/textchannel.cc
___
telepathy mailing list
telepathy
On 06/21/2016 11:38 PM, Diane Trout wrote:
> On Mon, 2016-06-20 at 12:33 +0300, George Kiagiadakis wrote:
>> Hi,
>>
>> I've taken the liberty of reviving a large portion of the old
>> telepathy
>> wiki and polishing some pages so that it's usable and more current.
yet. Thank you, I just
noticed that there is outdated link to Qt docs
(http://doc.qt.nokia.com/latest/). I'll investigate how it used and
fix it sometime soon.
Probably glib and spec docs can be updated via rsync too.
[1] https://telepathy.freedesktop.org/doc/telepathy-qt/
[2]
https://cgit.freedesktop.org/tel
On Mon, 2016-06-20 at 12:33 +0300, George Kiagiadakis wrote:
> Hi,
>
> I've taken the liberty of reviving a large portion of the old
> telepathy
> wiki and polishing some pages so that it's usable and more current.
>
> Take a look [1] and let me know what you thi
On Mon, 20 Jun 2016 12:33:08 +0300
George Kiagiadakis <gkia...@tolabaki.gr> wrote:
> I've taken the liberty of reviving a large portion of the old
> telepathy wiki and polishing some pages so that it's usable and more
> current.
For someone like me who is just finding his way i
Hi,
I've taken the liberty of reviving a large portion of the old telepathy
wiki and polishing some pages so that it's usable and more current.
Take a look [1] and let me know what you think. Feel free to edit it
further of course.
Regards,
George
[1]. https://telepathy.freedesktop.org/wiki
Thanks for explaining this. I didnt know much of this. :)
On Thu, Jun 16, 2016 at 1:33 AM, George Kiagiadakis <gkia...@tolabaki.gr>
wrote:
> On 06/15/2016 05:15 PM, Balram Pariyarath wrote:
> > A few days back my problem was that I cannot make any calls using
> > telepath
On 06/15/2016 05:15 PM, Balram Pariyarath wrote:
> A few days back my problem was that I cannot make any calls using
> telepathy (test-calls or msgs). Now I cant connect to my SIP acct. using
> empathy!
I'm sure there is an explanation to everything. Check the debug logs of
your c
error starting the call
I am facing simmilar issue.
https://lists.freedesktop.org/archives/telepathy/2016-June/006933.html
[1]
Are you guys both testing with Empathy as the frontend? Have you tried
testing calls with XMPP (telepathy-gabble) to see if empathy calls are
working in general?
In ad
sktop.org/archives/telepathy/2016-June/006933.html
> I am working on that.
> I just cloned the latest build of resiprocate1.10.0 and configured it.
But while I ran make check I got the following error.
>
> Makefile:1381: recipe for target 'test-suite.log' failed
> make[6]: *** [tes
On 14.06.2016 01:59, Tim Retout wrote:
Hi all!
I've used Telepathy for a long time, but I'm just starting to get
curious about addressing one of the bugs I've been encountering:
https://bugs.freedesktop.org/show_bug.cgi?id=45395 - wrong alias when
joining room
From my debugging over the past
Hi all!
I've used Telepathy for a long time, but I'm just starting to get
curious about addressing one of the bugs I've been encountering:
https://bugs.freedesktop.org/show_bug.cgi?id=45395 - wrong alias when
joining room
From my debugging over the past couple of evenings, it looks to me
like
> I have reached out to jdev mailing list, as well as the author of
> XMPP
> Desktop Screen Sharing in Empathy. Unfortunately I was not able to
> get
> any major attention.
I believe that the Empathy developers were also the original Telepathy
team as well, so its not surpri
omputer Science and Engineering (Batch: 2013-17)
> Govt. Model Engineering College, Kochi-21
>
> [image: ☎]: 8129130866
> ✉: balb...@gmail.com <p.balra...@gmail.com>
>
--
*Balram P MenonTech Head | Excel 2016*
Computer Science and Engineering (Batch: 2013-17)
Govt. Model Engineering College, Kochi-21
[image: ☎]: 8129130866
✉: balb...@gmail.com <p.balra...@gmail.com>
recent_bustle.pdf
Description: Adobe PDF document
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt/telepathy-qt-0.9.7.tar.gz
Signature:
http://telepathy.freedesktop.org/releases/telepathy-qt/telepathy-qt-0.9.7.tar.gz.asc
The "Back on track" release.
There is almost no client-side changes, just build fixes and a
on is good or bad.
Regards,
George
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
wrote:
>
> [...]
>
>>>
>>> #2 CM should not be named after the implementation because that can also
>>> lead to confusion between the two projects (the telepathy CM and the
>>> implementation software). See the example of telepathy-sofiasip that
>>&
the two projects (the telepathy CM and the
implementation software). See the example of telepathy-sofiasip that
became telepathy-rakia (mentioned in the spec as well). This is also a
factor against telepathy-ring (or telepathy-ring.cx perhaps) because
ring.cx is another software. You don't want users
On 12/06/16 08:24, George Kiagiadakis wrote:
> On 12.06.2016 07:26, Mateus Bellomo wrote:
>> Hello,
>>
>> I'm looking to implement the text message functionality (send/receive)
>> at resiprocate and I'm going through telepahty-morse [1] and
>> telepathy-no
Hello,
I'm looking to implement the text message functionality (send/receive) at
resiprocate and I'm going through telepahty-morse [1] and
telepathy-nonsense [2] implementations. I saw that both created a separated
class called textchannel.
I just want to confirm: to implement the text message
1 - 100 of 4694 matches
Mail list logo
