From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16102 invoked by alias); 1 Apr 2010 17:41:53 -0000 Received: (qmail 15923 invoked by uid 48); 1 Apr 2010 17:41:35 -0000 Date: Thu, 01 Apr 2010 17:41:00 -0000 Message-ID: <20100401174135.15922.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug other/43620] Uploading to gnu.org will fail due to automake security issue In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "rwild at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-04/txt/msg00119.txt.bz2 ------- 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