Difference between revisions of "User:Dfaure/MovingOnProjectKdeOrg"

Jump to: navigation, search
(Fixing scripty)
(Fixing build.kde.org)
Line 15: Line 15:
 
== Fixing build.kde.org ==
 
== Fixing build.kde.org ==
  
The job descriptions on build.kde.org usually have the projects.kde.org full URL in two places, which need to be fixed: description and repository browser further down. Then the project should be rebuilt, in all configurations.
+
The job descriptions on build.kde.org usually have the projects.kde.org full URL in two places, which need to be fixed: description and repository browser further down.
 +
Then ssh to all slaves and run this command:
 +
<pre>
 +
rm ~jenkins/scripts/kde_projects.xml
 +
</pre>
 +
Then rebuild the project on build.kde.org in all configurations (stable, qt4, qt5, not so stable... everything).
 +
 
 +
Monitor [http://build.kde.org/view/FAILED/ build.kde.org] to make sure nothing new fails.
  
 
== Fixing scripty ==
 
== Fixing scripty ==

Revision as of 10:59, 25 April 2014

This page lists all the steps that should be taken when moving a repo in the projects.kde.org structure.

On projects.kde.org

An admin (e.g. David or Ben) is needed to go to the project on http://projects.kde.org, Settings, Information, and change the location in the combobox.

kde-build-metadata

Search/replace from the old location to the new, in all files.

kdesrc-build

Adjust kf5-*-include for the new repo location. Usually this means removing special cases :)

Fixing build.kde.org

The job descriptions on build.kde.org usually have the projects.kde.org full URL in two places, which need to be fixed: description and repository browser further down. Then ssh to all slaves and run this command:

rm ~jenkins/scripts/kde_projects.xml

Then rebuild the project on build.kde.org in all configurations (stable, qt4, qt5, not so stable... everything).

Monitor build.kde.org to make sure nothing new fails.

Fixing scripty

If the repo is already translated, you need to fix scripty. Check out svn+ssh://[email protected]/home/kde/branches/stable/l10n-kde4/scripts and svn+ssh://[email protected]/home/kde/trunk/l10n-kde4/scripts

Usually when we move a module (from playground to kdereview to a final destination, for instance), all that needs to be done is to move all the .po files. Inform kde-i18n-doc so they know about the move and someone will take care of moving the .po files.

More complex cases involve moving modules for the Qt5/KF5 organization (frameworks/*, workspace/*). This makes the module disappear from kde4. The fix for that particular case is to re-add it by hand in the file get_paths, function list_modules, see the lines about kactivities.

If the repo moves between modules that are both listed in get_paths already, then the .pot will move between subdirs of "templates". This is an issue, since existing .po files get disconnected from the new template (.pot). Two solutions: either cheat in get_path to force the template back to where it was before, or move all .po files to the new location. It all depends on which location "makes sense" for this branch of l10n.


Content is available under Creative Commons License SA 4.0 unless otherwise noted.