Upstream repository shutdowns/Google code

This page intends to organize required actions to prepare the announced shutdown of Google code. 

Urgency
A wrong URL in an ebuild is a bug. It is necessary to prevent a manually written flood tickets in bugzilla. We do not have the manpower and the tools to manage 500 new, manually written bugs plus duplicates efficiently. Hence it is important that the ebuilds are fixed soon.

List of packages
or use the md5 cache

Security
Many projects got forked several times during the shut down procedure and it is not always easy to find out which fork is the right one for the Gentoo ebuild.

While many packages need an update to a new URL it is easy to plant silently a link to malicious source code instead of the original source code. It is also possible that a Gentoo developer uses a wrong fork by accident.

Brainstorming

 * First step: just 'clone' all SRC_URI to a random web server, and fix the current one to point at it.
 * Second step: figure out if the project has moved or has been frozen.

Statistics
In the case of BerliOS it took about one year to fix 50% of the ebuilds. Perhaps it is interesting to keep some statistics.

Command to collect date and number of packages with googlecode in the *URI variable:

A graph and the raw data is available on http://www.akhuettel.de/~huettel/plots/googlecode.php

Worklist

 * DONE 2016-10-28 Find out which packages need to be fixed exactly. Need bash scripts. jonasstein
 * DONE 2016-10-28 Create statistics on the progress. jonasstein,dilfridge
 * DONE 2016-11-05 send mail to gentoo-dev
 * TODO after 2016-12-11 send the mail to maintainers of remaining broken ebuilds
 * TODO after 2016-12-01 create bug tickets for remaining broken ebuilds
 * TODO Mirror all source files (tar balls...), add link here, add link to log which packages failed to mirror

Other repositories that were shut down
To learn from history:


 * BerliOS (70 ebuilds affected)
 * gitorious.org (26 ebuilds affected)