https://bugzilla.wikimedia.org/show_bug.cgi?id=66087
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #5 from [email protected] --- As we kicked symlink handling down the road for the backup script, and this card is now adding symlinks, this card needs to make the backup work with symlinks. Hence, reopening the bug. I had a short look, but it seems that wikimetrics generates absolute symlink targets, starting in /srv/wikimetrics/[...] instead of relative links. This use of absolute targets for symlinks unnecessarily binds the directory of public files to the full path where wikimetrics gets deployed to. Also, since the backup is currently grabbing the public files from /var/lib/wikimetrics, having the symlinks' absolute targets start in /srv/wikimetrics would make it necessary that the backup grabs files outside of its public directory. So it would make it hard for the backup to determine which targets of symbolic links are fine, and which are not. Could we use relative targets for links instead? That way, we could keep wikimetric's internal logic bound to the wikimetrics repository and would not need to duplicate this internal logic to the external backup script. And also, it would make the public files directory more portable. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
