public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rwild at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/43620] Uploading to gnu.org will fail due to automake security issue
Date: Thu, 01 Apr 2010 17:41:00 -0000	[thread overview]
Message-ID: <20100401174135.15922.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43620-15771@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from rwild at gcc dot gnu dot org  2010-04-01 17:41 -------
(In reply to comment #1)
> If no-dist works to pass the gnu.org check, that (unlike upgrades) should 
> be OK for 4.4 and 4.3 branches.

Well, for branches we are not in such a hurry.  I could easily release Automake
1.9.7 from branch-1-9 (which has only three non-documentation patches over
1.9.6) and upgrade 4.4 and 4.3 to that, if that is equally acceptable.

> I updated the maintainer-scripts/gcc_release script to use 755 instead of 
> 777 permissions, on trunk, 4.4 and 4.3 branches.  So there is no actual 
> security issue for future GCC releases.

Thank you.


-- 

rwild at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |rwild at gcc dot gnu dot org
                   |dot org                     |
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|0                           |1
      Known to fail|                            |4.3.5 4.4.4 4.5.0
           Priority|P3                          |P1
   Last reconfirmed|0000-00-00 00:00:00         |2010-04-01 17:41:35
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43620


  parent reply	other threads:[~2010-04-01 17:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 16:46 [Bug other/43620] New: " rwild at gcc dot gnu dot org
2010-04-01 16:50 ` [Bug other/43620] " joseph at codesourcery dot com
2010-04-01 17:41 ` rwild at gcc dot gnu dot org [this message]
2010-04-02 12:01 ` rguenth at gcc dot gnu dot org
2010-04-02 12:40 ` rwild at gcc dot gnu dot org
2010-04-02 12:44 ` rguenther at suse dot de
2010-04-02 18:19 ` rwild at gcc dot gnu dot org
2010-04-29 12:28 ` [Bug other/43620] [4.3/4.4 Regression] " jakub at gcc dot gnu dot org
2010-04-29 15:04 ` jakub at gcc dot gnu dot org
2010-04-30 18:26 ` [Bug other/43620] [4.3 Release Blocker] " jakub at gcc dot gnu dot org
2010-05-04 18:58 ` rwild at gcc dot gnu dot org
2010-05-06 17:21 ` rwild at gcc dot gnu dot org
2010-05-06 17:22 ` rwild at gcc dot gnu dot org

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=20100401174135.15922.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).