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 589425 - External deps release set?
External deps release set?
Status: RESOLVED FIXED
Product: damned-lies
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: damned-lies Maintainer(s)
damned-lies Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-07-22 19:59 UTC by Gabor Kelemen
Modified: 2009-08-01 11:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gabor Kelemen 2009-07-22 19:59:48 UTC
I tried to update our release sets according to the new module decisions (btw, how do I remove a category on the admin interface? :)), and I was just struck: where to put libgdata? It should go to the external dependencies set, but we don't have one. So, can we have one for those modules maintained in Gnome git?

These are, according to http://live.gnome.org/TwoPointTwentyseven/ExternalDependencies

http://l10n.gnome.org/module/conduit/
http://l10n.gnome.org/module/libgda/
http://git.gnome.org/cgit/libgsf/tree/ (not even tracked in d-l, gee)
http://l10n.gnome.org/module/libgdata/
http://l10n.gnome.org/module/system-tools-backends-clone/
Comment 1 Claude Paroz 2009-08-01 11:25:39 UTC
I added the libgsf module and the External Dependencies release set.