unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: 38422@debbugs.gnu.org, mhw@netris.org, bokr@bokr.com
Subject: bug#38422: .png files in /gnu/store with executable permissions (555)
Date: Sat, 30 Nov 2019 08:45:09 +0100	[thread overview]
Message-ID: <FCCE8805-6725-425D-99DE-4CCD2E00DCF4@lepiller.eu> (raw)
In-Reply-To: <871rtq57kd.fsf@netris.org>

Le 30 novembre 2019 05:08:55 GMT+01:00, Mark H Weaver <mhw@netris.org> a écrit :
>Hi Bengt,
>
>Bengt Richter <bokr@bokr.com> 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

Also, we should not encourage people to report bugs upstream directly. We have to evaluate whether the bug is on our side or theirs first to not drown them in useless bug reports :)

  parent reply	other threads:[~2019-11-30  7:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29  7:59 bug#38422: .png files in /gnu/store with executable permissions (555) Bengt Richter
2019-11-29  9:49 ` Ricardo Wurmus
2019-11-29 10:59   ` zimoun
2019-11-29 11:28   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-11-29 12:22   ` Bengt Richter
2019-11-29 12:20 ` Mark H Weaver
2019-11-29 15:03   ` Bengt Richter
2019-11-30  4:08     ` Mark H Weaver
2019-11-30  4:24       ` Brett Gilio
2019-11-30  7:45       ` Julien Lepiller [this message]
2019-11-30 20:07         ` Bengt Richter
2019-12-02 15:20           ` zimoun
2020-01-22  0:22 ` bug#38422: Bug status? '.png' files with executable permissions zimoun
2020-01-22  2:28   ` Bengt Richter
2020-01-27 19:55     ` zimoun
2020-01-22  0:31 ` bug#38422: zimoun

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FCCE8805-6725-425D-99DE-4CCD2E00DCF4@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=38422@debbugs.gnu.org \
    --cc=bokr@bokr.com \
    --cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).