After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 795335 - telepathy-glib is no longer needed by gnome-online-accounts
telepathy-glib is no longer needed by gnome-online-accounts
Status: RESOLVED FIXED
Product: gnome-continuous
Classification: Other
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: GNOME Continuous maintainer(s)
GNOME Continuous maintainer(s)
Depends on: 795322
Blocks:
 
 
Reported: 2018-04-17 15:39 UTC by Debarshi Ray
Modified: 2021-06-07 19:55 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
manifest: telepathy-glib is no longer needed by gnome-online-accounts (1.25 KB, patch)
2018-04-17 15:42 UTC, Debarshi Ray 		committed Details | Review

Description Debarshi Ray 2018-04-17 15:39:04 UTC 
Telepathy support has been removed from gnome-online-accounts. While it doesn't, or at least shouldn't, actually affect the build, it might be nice to move the telepathy-glib build later in the build order to make this more obvious.
Comment 1 Debarshi Ray 2018-04-17 15:42:20 UTC 
Created attachment 371064 [details] [review]
manifest: telepathy-glib is no longer needed by gnome-online-accounts

Untested patch.

I looked through the modules in the list, and I couldn't spot anything that's known to require telepathy-glib. However, I am not 100% sure since I didn't actually double-check and relied on my memory.
Comment 2 Emmanuele Bassi (:ebassi) 2018-04-17 15:43:58 UTC 
Review of attachment 371064 [details] [review]:

:+1:
Comment 3 André Klapper 2021-06-05 16:29:35 UTC 
gnome-continuous is not under active development anymore. Its codebase has been archived: https://gitlab.gnome.org/Archive/gnome-continuous

Closing all its open tickets as part of housekeeping.
Comment 4 Debarshi Ray 2021-06-07 19:55:41 UTC 
I had left this open by mistake. It was actually fixed when I committed the patch attached here.