From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id CN5YJS7yu2Lu8wAAbAwnHQ (envelope-from ) for ; Wed, 29 Jun 2022 08:33:18 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id qOJFJS7yu2LHfgAA9RJhRA (envelope-from ) for ; Wed, 29 Jun 2022 08:33:18 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 3A1292BE19 for ; Wed, 29 Jun 2022 08:33:18 +0200 (CEST) Received: from localhost ([::1]:42572 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o6QsG-0004Uy-4K for larch@yhetil.org; Wed, 29 Jun 2022 02:08:28 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:48308) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o6Qrw-0004TM-NZ for guix-devel@gnu.org; Wed, 29 Jun 2022 02:08:08 -0400 Received: from mailout.easymail.ca ([64.68.200.34]:37008) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o6Qru-0005cu-Fd; Wed, 29 Jun 2022 02:08:08 -0400 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 24F2D61FDF; Wed, 29 Jun 2022 06:08:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bokr.com; s=easymail; t=1656482884; bh=y/g38jQMkZQg5mXNVHnhcKKoTUfaRApoUTCf8xO8EzI=; h=From:Date:To:Cc:Subject:References:In-Reply-To:From; b=iEclGW6lTRv6bFMcA5GZrbkSmHuKjDYQKVFsW9QPwM9uh0fCZ7DDMCP+ACY8URzFn OHCJUhHvk+xyErQw1WREBRRJKb617NGxq6RQlVCPdGWx/R7KsGeqH/KHBpWp4eQLuc vUXKR+SK1IsXREIkLkPMZVGq1YZN1lWGk9xh75avrJKr+6rMqJM2mhdMmhOSWeS2Y6 wpaGI0INzjxDCeHdgHstgMBa+1cpTYx4gIP70dKAbZ7TbpWYMHlPRaeJ5v9W5gTTvm mDdCZEVgCYIhi62B95py7zKNIMXlzyciRxAOaMaNGHw3Hvdp1WQYZjQVDUHZ8EYnxJ OyADr28AqOiiQ== X-Virus-Scanned: Debian amavisd-new at emo09-pco.easydns.vpn Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo09-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wnLAU3jtQjKV; Wed, 29 Jun 2022 06:08:03 +0000 (UTC) Received: from localhost (m83-185-44-184.cust.tele2.se [83.185.44.184]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 434B761F33; Wed, 29 Jun 2022 06:08:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bokr.com; s=easymail; t=1656482883; bh=y/g38jQMkZQg5mXNVHnhcKKoTUfaRApoUTCf8xO8EzI=; h=From:Date:To:Cc:Subject:References:In-Reply-To:From; b=lI8vjivXWVL78AMsfJs+6hP+YMSXACDtgxSncPHOTIv1Jme7M8WmdeAmbXtlqg+CH SI929bcgXUkv4qm0UKdP7lnWAsALRq/NTuUhN9VAZ7+KEVHheXyIovCJI+Wk6yqjdr /UzLdGnwn4+IjKoZTtbyYVjAcqT6Fa+Vr+fls4z17ReUw4GVWEnjWKVf8Qyg7QUVxV snm1w6RRyn8S7XCpHXJ/rAvHc3n2XYDGH7s0aA6VSt4JRlQxRgdqOnuf+5tnlWUPAq dxOIEkQECjzL6pgxaaE6B+BVklzHAq2GwYG5qh1egJr3JkOamiVUb9Xg2iuuiVA/ND RroYJKUYPDlcQ== From: bokr@bokr.com Date: Wed, 29 Jun 2022 08:07:10 +0200 To: zimoun Cc: Maxime Devos , Ludovic =?utf-8?Q?Court=C3=A8s?= , Tobias Kortkamp , guix-devel@gnu.org Subject: Re: Dealing with upstream issues Message-ID: <20220629060710.GA17675@LionPure> References: <6d31ff958ec0c75cbba8324a275315d195a54902.1653045472.git.tobias.kortkamp@gmail.com> <87sfntu6ft.fsf@gnu.org> <87r13aifi3.fsf_-_@gnu.org> <6d2b1052b3e63a67c42c4e6ce431b3f1bb4b4605.camel@telenet.be> <865yklf3vq.fsf@gmail.com> <2dc71c54541e84a647187fb0e6e34672930b697a.camel@telenet.be> <86ilokeowu.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86ilokeowu.fsf@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-13) Received-SPF: pass client-ip=64.68.200.34; envelope-from=bokr@bokr.com; helo=mailout.easymail.ca X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1656484398; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=zkTobAwaSEvOLoENSmB18JIqm/koLoFEpjAq4wBhGi4=; b=m6CE0btsePJFHI9f8w9BB5H7UL+3wYdxNFEcvu+oXxIrp6eU0Ru7yripEL12+Z2xt3Yvzm lEy/01FXwAjOCoIYfCZ8Kp+3kSU7ySzwM4gW2uibDko19011SJZ7vDU1Gk31InxzlFW1zM 3Oj7JxqsIMB3rvkpGHRxOscky/YKEO6qd0UUpAjFqiAy7lBgqkUV5UMf7NznEc5Fwgu7TO rbThvR4/O6GEyswOdtsovSyR0mgB0ZcGp5Ze2lLl52QnVYe8SZXGRIUvsUr3WGLlb0ld8z MJTJPOPG4VwGu4m3RbamCFtZx3FlBdYvIfOumZcakZAsh2aWtXQ1sxScWeUWPQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1656484398; a=rsa-sha256; cv=none; b=BcpugvD/Iag0K4DJ6Mv9nGdrdgtOh5e23atHRKt3t/TB6UYtiQx3etWdKj0GLcSpudmmP4 uEf/vnYUpWGMzPTZEnfp7zvoaeR0wNvSmV2oCHhb48RMOwfdZuRASRDEVpy6wP61jZeeTD qXNnnPdSk4+63iIQgb0DXjIPIkZKSCPWVzN+2REuCNkkbLDUEqX1dpUvjiUTZnkTSXCVKZ Euodcqe/ROEjv7SNDJdZPYbU/HNh4iHTNSqrlwhMUEtCueV7XOluga+xq2dYV9RETZOTBk dNb8fHP2Gsr67Xh6QSSUVq+4Kjk9W2NtdqsBmem34l55fwFHSsfmhkPZXLuZcw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=bokr.com header.s=easymail header.b=iEclGW6l; dkim=fail ("headers rsa verify failed") header.d=bokr.com header.s=easymail header.b=lI8vjivX; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: 4.24 Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=bokr.com header.s=easymail header.b=iEclGW6l; dkim=fail ("headers rsa verify failed") header.d=bokr.com header.s=easymail header.b=lI8vjivX; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 3A1292BE19 X-Spam-Score: 4.24 X-Migadu-Scanner: scn0.migadu.com X-TUID: 09sN4pDii6qp Hi zimoun, et al, On +2022-06-28 18:25:05 +0200, zimoun wrote: > Hi, > > On Tue, 28 Jun 2022 at 14:31, Maxime Devos wrote: > > > You often close bugs with as rationale: ‘no response since X months, > > hence closing’, so it seems to me that you would simply close bug > > reports if the bug reporter is gone. > > [...] > > > That's the issue I wanted to highlight -- issues are closed before > > being fixed when the the reporter disappears (and hence, cannot provide > > "more info", or has other things to do than provide a fix by > > theirselves), even if the bug is understood. > > These claims are inaccurate. And it appears to me unfair considering > all the amount of time I personally spend on old bug triage; instead of > doing other (funner?) things. > > My workflow dealing with old bugs is: pick one and read the report (and > the complete thread, if any), then, > > 1. the report provides enough information for reproducing; I try to > reproduce myself and report more info, and then I try to collaborate > for fixing or closing. > > 2. the report does not provide enough information to understand what > the bug is about or to find a way to reproduce; then I ask more info > – sometimes my reply is even the first one, then, > > a) an answer is back so it is similar as #1. > > b) no answer after 2 or more weeks, so I try to determine if the > report is actionable and if the next action is fine-grained > enough to be doable. After 2 or more weeks, I ask again. > > Therefore, if a bug report after 2 or 3 years is not commented, > especially after 2 or more attempts to understand and ask for the > next steps without an answer back by the whole community, what > could be the action other than just close the report. > Nothing, except maybe special archiving, or tagging for indexing? By bug closing time, you have typically produced the best summary of the bug chase, with clues and tips and examples for reproducing and links where to find more info, such as links to Ludo's (particularly, but others too) debugging examles. ( Kudos and thanks :) So it's a matter of making sure your valuable work is archived for easy use in future bug chases, ISTM. Of course, your posts /are/ archived in the mailing lists. (I like the POP3 mbox-format archives, where it's easy to grep the headers. I do wget -c to make myself copies of selected mail list months, so I can search offline and view with mutt. What I'd like is something in the Subject: line to make it greppable for /both/ what the bug is about and how it was closed, i.e. bug status. Maybe if a post that says "closing" could have "[closing: ]" in the Subject: line, where could say "fixed upstream" or "unresolved" or whatever (bikeshed for dev ideas?). Then you could use "[closing: unresolved]" in the closing post Subject: line for a case that withered from inattention, (your 2b) but still looks suspicious (if you think so). E.g. suspicious like an fseg that went away because new linkage for an update made the bad write clobber something still, but without fseg: It would be misleading to mark that "fixed" IMO. Maybe "disappeared" :) Anyway, the idea is to make the Subject: line greppable for both what the bug is about and its status when it was closed. > Ultimately, nothing is perfect and people are doing their best with > their resource at hand; at least, I do my best with the resource at my > hands. I would be more than happy if more people would try to sort, > classify or fix the old bugs. Maybe, you will join the effort ? > > I stop now the discussion in this thread since I do not see what we are > discussing. > > Cheers, > simon > -- Regards, Bengt Richter