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 646956 - Upgrade Planet software to git head
Upgrade Planet software to git head
Product: website
Classification: Infrastructure
Other Linux
: Normal normal
: ---
Assigned To: Planet GNOME maintainers
Planet GNOME maintainers
Depends on:
Reported: 2011-04-06 21:12 UTC by Olav Vitters
Modified: 2014-05-08 11:55 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Olav Vitters 2011-04-06 21:12:58 UTC
Latest PlanetPlanet code was forked as Venus and available at:

It includes some fixes to enable threading. We should investigate switching to this.
Comment 1 Olav Vitters 2011-04-07 08:34:34 UTC
Seems faily easy. It already uses Venus from June 2010. Going to commit a patch which ensures Venus is automatically installed on the machine hosting
Comment 2 Alberto Ruiz 2011-04-07 09:22:39 UTC
Does it use the same template system?
Comment 3 Olav Vitters 2011-04-07 09:26:45 UTC
Everything is exactly the same. Just a newer version. Plus not relying on software installed in a home directory.

FWIW, already made the switch :)

Currently testing it
Comment 4 Alberto Ruiz 2011-04-07 10:19:17 UTC
You are a star :-)
Comment 5 Alberto Ruiz 2011-09-24 21:24:48 UTC
Is this finished Olav?
Comment 6 Baptiste Mille-Mathias 2012-02-23 16:23:27 UTC
Olav, what is the status of this tracker ?
Comment 7 Daniel Mustieles 2014-01-12 22:13:17 UTC
Hey, can we close this bug?
Comment 8 Daniel Mustieles 2014-05-06 10:56:34 UTC

Which is the status of this issue?

Comment 9 Andrea Veri 2014-05-06 20:35:17 UTC
git clone gnome:planet-web 
cd planet-web
git remote add venus (from
git pull venus master

 * branch            master     -> FETCH_HEAD
Already up-to-date.

Seems we are running the latest and greatest, no new commits since 2011 from what I can see. Should we mark this as resolved?
Comment 10 Daniel Mustieles 2014-05-08 11:55:39 UTC
Yes, in this case we can close the bug as resolved.

Thanks for taking care of this! :)