Bug#1082010: libgdata: unmaintained upstream

[Simon McVittie]

On Tue, 17 Sep 2024 at 09:56:03 -0400, Jeremy Bícha wrote:
> My opinion is that libgdata is the most critical thing blocking
> removal of libsoup2.4 from Debian.

Indeed.

> I think the Google Drive integration is very useful and it would be a
> shame to lose it.

Let's leave it in gvfs if someone (most likely Alessandro Astone?) can
fix the libgdata build for time64 and updated json-glib, but consider
it to be "at risk".

> There were other apps that had extra Google
> integration like gnome-photos but those were lost when libgdata wasn't
> ported to libsoup3

I think we should try to remove the unused libgdata-dev build-dependency
from these, so that we have a more realistic picture of what is actually
using libgdata. I've started looking at some of the GNOME Team packages
in this situation, but it would be better if someone who is a regular
user of the relevant packages could test and upload.

> Except for the libsoup issue, I didn't have other problems with libgdata.

My problem with it is that it seems to be de facto unmaintained upstream.
If the Google Drive integration in gvfs is important, perhaps someone
from Canonical could look after it?

    smcv