> - I don't understand the line `/usr/lib/purple-2*/`.
You are right. Telegram-purple only creates /usr/lib/purple-2/, so
asterix can be removed. In fact I think we don't need
"/usr/lib/purple-2*/ r", as "/usr/lib/purple-2/*.so mr", will do the
job.
> telegram-purple is supposed to detect telepathy, and avoid the path
> `@{HOME}/.purple/telegram-purple/`. Was it really necessary?
It should but it doesn't at the moment.
And yes, it is necessary with 1.3.x. The plugin stores data after
authentication in either @{HOME}/.purple/telegram-purple/ or @{HOME
}/.telegram-purple/ depending on plugin version number. So telepathy-
haze would require read/write access to that folder, otherwise apparmor
give access-denied and users have to re-authenticate each time after
opening the client (empathy).
I will update the patch. Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375
Title:
Add support for purple-telegram (telepathy-haze)
Status in telepathy-mission-control-5 package in Ubuntu:
New
Bug description:
When using purple telegram through telepathy-haze, it requires
following permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.so mr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
