when doing a staging release of 3.6rc1, it came to light that rysnc versions are 2.6.8 on aus2-staging, vs. 2.6.3 on staging-stage and the staging-stage version does not have the -O flag that is needed for pushsnip: echo Running $RSYNC -PaO $STAGING_DIR/$1/ $LIVE_SNIPPET_DIR $RSYNC -PaO $STAGING_DIR/$1/ $LIVE_SNIPPET_DIR
If it's only causing a warning then that's completely fine. We need -O for aus2-staging to make sure the snippets appear on quickly on aus2.m.o. (nfs mounts are used, and without the switch the directories get the modification times from the snippet generation. That plays badly with nfs caching, which compares the mtime on the dir with some internal marker. With -O the dirs get the current time when you push, and the nfs knows to refresh the cache.)
it causes a failure: Running /usr/bin/rsync -PaO /opt/aus2/snippets/staging/20091120-Firefox-3.6rc1-test/ /opt/aus2/incoming/3 rsync: -PaO: unknown option rsync error: syntax or usage error (code 1) at main.c(1084)
Urgh. This is a CentOS 4.4 box and rsync v2.6.3 is the best we can do without a manual compile. Time to update to the linux refimage ? AFAICT it's providing ftp.m.o and aus2-staging.m.o functionality so the re-setup wouldn't be too bad.
Did the following on staging-stage to install v 2.6.8 of rsync: wget http://centos.mirror.iweb.ca/5.4/os/SRPMS/rsync-2.6.8-3.1.src.rpm rpmbuild --rebuild rsync-2.6.8-3.1.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/rsync-2.6.8-3.1.i386.rpm Putting the -O back in staging-stage's pushsnip and closing this.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.