From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 126412 invoked by alias); 30 Apr 2015 16:34:50 -0000 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 Received: (qmail 126363 invoked by uid 48); 30 Apr 2015 16:34:47 -0000 From: "LpSolit at netscape dot net" To: gcc-bugs@gcc.gnu.org Subject: [Bug web/64968] Upgrade GCC Bugzilla to 5.0 Date: Thu, 30 Apr 2015 16:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: web X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: LpSolit at netscape dot net X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: LpSolit at netscape dot net X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-04/txt/msg02671.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D64968 --- Comment #28 from Fr=C3=A9d=C3=A9ric Buclin --- Maybe is this a coincidence, but all bugmails I found which have a wrong timestamp have something in common. First of all, the offset is *always* the same: -05:30. Then, it seems the problem only happens when the clock is clo= se to :15, :30, :45 or :00, as shown below: Markus Trippelsdorf 2015-04-28 16:14:58 UTC H.J. Lu 2015-04-28 16:19:15 UTC Andreas Schwab 2015-04-28 20:20:10 UTC Christian Eggers 2015-04-29 15:59:49 UTC Jonathan Wakely 2015-04-30 09:14:14 UTC Rainer Emrich 2015-04-30 13:45:19 UTC @Markus: no need to paste the full email header anymore as I'm getting all bugmails myself since last night. Just indicate the bug ID and comment ID (= or real timestamp if it's not a new comment), and I will find it. :) @overseers: to be honest, I don't think this is a bug in Bugzilla itself. I would tend to a bug or a bad interaction with the MTA, qmail or sendmail. Is sourceware running some cron job every 15 minutes, which could interact with Bugzilla sending emails at the same time? And depending on which job is run, maybe sendmail/qmail is confused and uses the wrong timezone. No idea why t= he offset is always -05:30, but this may give sourceware admins some clue. >>From gcc-bugs-return-485120-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 30 16:35:01 2015 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 129464 invoked by alias); 30 Apr 2015 16:35:01 -0000 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 Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 129146 invoked by uid 48); 30 Apr 2015 16:34:57 -0000 From: "dominiq at lps dot ens.fr" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65931] [5/6 regression] dsymutil assertion failure building libgnat-5.dylib Date: Thu, 30 Apr 2015 16:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: dominiq at lps dot ens.fr X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-04/txt/msg02672.txt.bz2 Content-length: 560 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65931 Dominique d'Humieres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-04-30 Ever confirmed|0 |1 --- Comment #2 from Dominique d'Humieres --- I have already filed Bug ID# 20510039 and I am using dsymutil from Xcode 6.2.