Dear Savannah Hackers, and GNU.org sysadmins, In the public ticket 108855 I raise the issue that the synchronization script between Savannah and the GNU.org website is broken.
https://savannah.gnu.org/support/index.php?108855 Every 6 months for a glibc update we remove the old manual, build a new manual, and install the new manual. Since we started this process the sync script has always gotten something wrong. It looks like a concurrency issue where the old removal is still running while the new update arrives and what is left is a big mess. We have two solutions: (a) Fix the sync script to work properly. (b) Operate on different directories. I have not received any traction for (a) in bug 108855 from any responsible party. This issue will clearly impact any GNU project using savannah to host their website. I would like to keep hosting glibc on gnu.org since it's a core gnu project and an important one. To that end I'm considering (b), which is to generate a new docs directory for ever release and thus avoid two operations on the same path on the remove server. This means we would be growing the storage required for the website by ~100MB/year. We might eventually retire the old releases as cleanup when we reach some consensus over that. Does anyone see any problem with (b)? I haven't tried it yet, but will do so shortly. Cheers, Carlos.
