public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Cc: Jakub Jelinek <jakub@redhat.com>
Subject: [PATCH (pushed)] maintainer-scripts: fix superfluous 'sh' for Python script
Date: Thu, 10 Nov 2022 06:38:50 +0100	[thread overview]
Message-ID: <6a787a97-83e1-151c-a5ee-3dd03e82d844@suse.cz> (raw)

Hi.

I noticed:
https://gcc.gnu.org/pipermail/gccadmin/2022q4/019260.html

/home/gccadmin/venv/bin/python3: /home/gccadmin/venv/bin/python3: cannot execute binary file

It will be fixed with the following patch.

@Jakub: Please update the cron.

Thanks,
Martin

maintainer-scripts/ChangeLog:

	* crontab: Fix superfluous 'sh' for Python script.
---
 maintainer-scripts/crontab | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/maintainer-scripts/crontab b/maintainer-scripts/crontab
index 09e33c0095f..0fd885ea759 100644
--- a/maintainer-scripts/crontab
+++ b/maintainer-scripts/crontab
@@ -1,5 +1,5 @@
 16  0 * * * sh /home/gccadmin/scripts/update_version_git
-50  0 * * * sh /home/gccadmin/venv/bin/python3 /home/gccadmin/scripts/update_web_docs_git.py /www/gcc/htdocs/onlinedocs/ --sphinx-build=/home/gccadmin/venv/bin/sphinx-build
+50  0 * * * /home/gccadmin/venv/bin/python3 /home/gccadmin/scripts/update_web_docs_git.py /www/gcc/htdocs/onlinedocs/ --sphinx-build=/home/gccadmin/venv/bin/sphinx-build
 55  0 * * * sh /home/gccadmin/scripts/update_web_docs_libstdcxx_git
 32 22 * * 4 sh /home/gccadmin/scripts/gcc_release -s 10:releases/gcc-10 -l -d /sourceware/snapshot-tmp/gcc all
 32 22 * * 5 sh /home/gccadmin/scripts/gcc_release -s 11:releases/gcc-11 -l -d /sourceware/snapshot-tmp/gcc all
-- 
2.38.1


                 reply	other threads:[~2022-11-10  5:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a787a97-83e1-151c-a5ee-3dd03e82d844@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).