From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) by sourceware.org (Postfix) with ESMTPS id F2C5038618FC for ; Tue, 30 Jun 2020 14:52:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org F2C5038618FC Received: by mail-qk1-x72b.google.com with SMTP id r22so18779045qke.13 for ; Tue, 30 Jun 2020 07:52:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=YUKh0g1/IWj/LAkSb6PDW/TCTkpdSG9W+84SrGhXUS0=; b=o0EQ2eNQmtw04FktyfkdaE335w1DhsTuQDB/UoXEszu4GzJ96p+KkDhvao1Rq89c3R 5vGBr9D3aBLBGbfNFn30xAuSiiXon1iNjPp4K+atpdo11bEI0eYwB6mNjVoEU8PC2zj0 56FE0ePm0wWcXn+CnZz9/gc73GN/xIHy7npFO0vaNyH63VRfdeJlauZ11okYK7kvw1CX TI7XNyg1bA4KlGjDMZzFyKmUaj7BGy6HAy3I9eP6BxjWgUNs5rrZyf+GEVXIV4qqS04B 6Xd4xvU4H0P37JuDgjXhhzRDm01ig7IPWVA3QThZ2Sy/B+XprnpRY6n3/qXT0c3HOcYR 8enA== X-Gm-Message-State: AOAM533tZmFDWVNSxtDczNV8ay+ljDcDzsQ/0U0eyric8X6P/kr5MHwu rXEf6+4UkXeRu/OccE09kncgV4Ib X-Google-Smtp-Source: ABdhPJyNAV7IxJELbuuJwMsEdqf4OFwo8y39MlVUzBpvwrMxOXQUPIV08aPNZqlA7Ftf7H7GFFgIPw== X-Received: by 2002:a05:620a:2158:: with SMTP id m24mr20245979qkm.494.1593528728586; Tue, 30 Jun 2020 07:52:08 -0700 (PDT) Received: from [192.168.0.41] (184-96-233-25.hlrn.qwest.net. [184.96.233.25]) by smtp.gmail.com with ESMTPSA id u5sm3165217qke.32.2020.06.30.07.52.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 30 Jun 2020 07:52:07 -0700 (PDT) Subject: Re: Strange gcc bugzilla errors To: Overseers mailing list , "overseers@gcc.gnu.org" Cc: Thomas Koenig References: <4914173f-ab83-fa8f-ed3c-9c1eb3cde4d5@netcologne.de> From: Martin Sebor Message-ID: Date: Tue, 30 Jun 2020 08:52:06 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <4914173f-ab83-fa8f-ed3c-9c1eb3cde4d5@netcologne.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2020 14:52:10 -0000 On 6/30/20 1:47 AM, Thomas Koenig via Overseers wrote: > Hi, > > since today, I keep getting strange bugzilla errors when submitting > a comment to the gcc bugzilla.  The comments do appear. > > One example where this happened is > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95366#c4 > > Here is the error message: > > Software error: > > Invalid Content-Type 'subtype' parameter at Bugzilla/BugMail.pm line 471. > > For help, please send mail to the webmaster (root@localhost), giving > this error message and the time and date of the error. Just confirming that I have seen the same error yesterday. Comment #5 is a duplicate of c#4. I submitted it twice thinking the error was transient. I got it after both submissions. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95940 Martin