According to comments on
<https://gitlab.gnome.org/GNOME/libgdata/-/merge_requests/47>,
libgdata is effectively unmaintained upstream. I am not aware of any
obvious replacement.

Several packages in Debian depend on it and would be broken by its
removal, but its uses in most of them are trivial/obsolete:

Genuine(?) uses
---------------

- gvfs has a runtime dependency, for the Google Drive plugin. This could
  be disabled by compiling with -Dgoogle=false if desired.

- gnome-shell-extension-gsconnect Recommends the GIR typelib. I haven't
  investigated further.

Obsolete references
-------------------

- eog-plugins Build-Depends on libgdata-dev but doesn't use it any more
  (it's for a plugin for Google PicasaWeb, which was disabled after
  Google discontinued the web service).

- gnome-photos Build-Depends on libgdata-dev but doesn't use it any more
  (the plugin was disabled in order to avoid a libsoup2 / librest 0.7
  dependency)

- grilo-plugins Build-Depends on libgdata-dev, but there's a change staged
  in its git repo to remove the build-dependency

- shotwell Build-Depends on libgdata-dev but I don't see any sign that
  it's used, maybe a plugin was removed?

- totem Build-Depends on libgdata-dev but I don't see any sign that
  it's used, maybe a plugin was removed?

I think we should seriously consider removing this from trixie.

    smcv

My opinion is that libgdata is the most critical thing blocking
removal of libsoup2.4 from Debian. I was intending to have it removed
from Testing after Trixie is released if
https://gitlab.gnome.org/GNOME/libgdata/-/merge_requests/49 hadn't
been resolved by then.

https://release.debian.org/transitions/html/libsoup3.html
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-gnome-maintainers%40lists.alioth.debian.org&tag=libsoup2

I think the Google Drive integration is very useful and it would be a
shame to lose it. There were other apps that had extra Google
integration like gnome-photos but those were lost when libgdata wasn't
ported to libsoup3 and apps can't directly link against libsoup2.4 and
libsoup3.

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

Thank you,
Jeremy Bícha

Indeed.

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".

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.

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

As gvfs is no longer built with libgdata, make this an RC bug.

Dear submitter,

as the package libgdata has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1111560

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)