Skip to content

Pootle FS migration snaglist

Dwayne Bailey edited this page Aug 29, 2017 · 9 revisions

Focused on the migration from project_tree to pfs

Background setup

I have four projects: gnu, nongnu and autognu, autonongnu. These all align with the project tree styles that can be selected. These are initially setup on a stable/2.8.x based Pootle then migrated to current master

Issues

  • Post migration:
    • None/<language_code>.<ext> is the Translation path mapping for gnu project after migrations. While /<language_code>.<ext> is the mapping for autognu
    • Project state is untracked. Do pootle fs fetch nongnu then pootle fs state nongnu and then the project state is Untracked files (1). I'm not sure if this is intentional, but requires quite a fast learning curve. My assumption would be that after this migration the files are in sync, perhaps that is too risky but it would eliminate a lot of risk.

Other Issues

Not directly related to the migration.

  • sync from Pootle to FS doesn't update PO last translator header
Clone this wiki locally