Paul Wise wrote: > I run github-backup from cron to backup all repositories that I have > access to. It is too verbose to run from cron. So I tried redirecting > stdout to /dev/null. It still complains every day about the > whowatch.wiki.git repository not existing and then returns an error. It > is pretty normal for github projects to not have an associated wiki so > the warning should happen on stdout and not result in an error. > Alternatively, it would be nice to have a --quiet option that disables > normal output, ignores errors about missing wiki repositories and leaves > other error messages in place. > > pabs@chianamo ~/backup/repositories/github $ github-backup pabs3 > /dev/null > fatal: > https://github.com/mtsuszycki/whowatch.wiki.git/info/refs?service=git-upload-pack > not found: did you run git update-server-info on the server? > error: Could not fetch github_mtsuszycki_whowatch.wiki
github-backup only tries to clone from a wiki when the github API says the repository has one. Unfortunately their API seems to sometimes say that even when it doesn't exist. So the only way github-backup can find out is to try to clone it. If the clone fails, it does not treat this as an error, because the API is known to give bad information. Using github-backup with chronic from moreutils should work well. -- see shy jo
signature.asc
Description: Digital signature
