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] New: Uploading to gnu.org will fail due to automake security issue
Date: Thu, 01 Apr 2010 16:46:00 -0000 [thread overview]
Message-ID: <bug-43620-15771@http.gcc.gnu.org/bugzilla/> (raw)
The Automake 'make dist' security issue in 1.11 (fixed in 1.11.1) will likely
prevent uploading to gnu.org, even though GCC does not use the rule.
See here: <http://sourceware.org/ml/binutils/2010-03/msg00452.html>.
Using no-dist throughout, or updating to 1.11.1, should be possible, or talking
to the gnu.org admins. The update to 1.11.1 is really trivial for trunk, but
for older branches, some other strategy would need to be used.
I'm working on a patch.
CC:ing a RM.
--
Summary: Uploading to gnu.org will fail due to automake security
issue
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: blocker
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rwild at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43620
next reply other threads:[~2010-04-01 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 16:46 rwild at gcc dot gnu dot org [this message]
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
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=bug-43620-15771@http.gcc.gnu.org/bugzilla/ \
--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).