From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#38422: .png files in /gnu/store with executable permissions (555) Date: Fri, 29 Nov 2019 23:08:55 -0500 Message-ID: <871rtq57kd.fsf@netris.org> References: <20191129075938.GA55971@PhantoNv4ArchGx.localdomain> <878sny6fgr.fsf@netris.org> <20191129150329.GA80736@PhantoNv4ArchGx.localdomain> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:49839) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iau64-0003II-07 for bug-guix@gnu.org; Fri, 29 Nov 2019 23:11:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iau62-0003HN-Vc for bug-guix@gnu.org; Fri, 29 Nov 2019 23:11:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:55974) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iau62-0003Ft-KD for bug-guix@gnu.org; Fri, 29 Nov 2019 23:11:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iau62-0007bw-5R for bug-guix@gnu.org; Fri, 29 Nov 2019 23:11:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20191129150329.GA80736@PhantoNv4ArchGx.localdomain> (Bengt Richter's message of "Fri, 29 Nov 2019 07:03:29 -0800") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Bengt Richter Cc: 38422@debbugs.gnu.org Hi Bengt, Bengt Richter writes: > On +2019-11-29 07:20:41 -0500, Mark H Weaver wrote: >> The proper solution is to send bug reports to the upstream developers of >> docbook-xsl, faba-icon-theme, and moka-icon-theme, asking them to fix >> the permissions of the *.png files in their source tarballs. >> > That I haven't done. Is there a standard way to do it? No. > "guix show moka-icon-theme" tells me homepage, but it would be nice > to have a guix show --verbose that would show bug reporting info :) It would be nice, but it would also be an enormous amount of work. First we'd need to devise a way to represent that information, and then we'd need to add it to each of our 10K+ packages. It would also be an additional job to do when adding new packages. I'm not sure it's worth all that work. We already record the home page, and from there it's usually not much work to find how to report bugs. In cases where it _is_ difficult to find out how to report bugs, that's arguably a problem that should be fixed upstream. What do you think? Regards, Mark