From: Brendan Tildesley via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "37955@debbugs.gnu.org" <37955@debbugs.gnu.org>
Cc: "mail@ambrevar.xyz" <mail@ambrevar.xyz>
Subject: bug#37955: warning: '.desktop' file refers to '', which cannot be found
Date: Fri, 9 Apr 2021 12:56:35 +0200 (CEST) [thread overview]
Message-ID: <1448605157.72653.1617965795461@office.mailbox.org> (raw)
In-Reply-To: <87pnihfevc.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
The Exec paths in these files already refer to absolute paths, infact, /gnu/store paths
Thus the regex:
("^Exec=([^/[:blank:]\r\n]*)(.*)$" _ binary rest)
with binary = empty string and rest = everything after Exec=
Why? The second subexpression [^/[:blank:]\r\n]* is bound to binary, but it means anything
that is a series of anything that is not /, space, or newline. absolute paths start with /, so it matches nothing (empty string), and continues to call (which "").
I notice this phase hasn't been edited in 5 years and has other issues, for example:
1. patch-dot-desktop-files only searches the output of the package for paths, not the inputs. This means for example xfce4-settings fails to patch references to exo-open in desktop files.
The code should be remade to be more /correct/, and handle all unexpected inputs. In this case the phase is accidentally doing the right thing by failing in a harmless way and correctly not patching the files, but emitting a warning.
[-- Attachment #2: Type: text/html, Size: 1947 bytes --]
next prev parent reply other threads:[~2021-04-09 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 8:33 bug#37955: warning: '.desktop' file refers to '', which cannot be found Pierre Neidhardt
2021-04-09 10:56 ` Brendan Tildesley via Bug reports for GNU Guix [this message]
2021-04-09 11:23 ` Pierre Neidhardt
2021-04-09 11:53 ` Brendan Tildesley via Bug reports for GNU Guix
2021-04-09 17:39 ` Pierre Neidhardt
2021-04-10 1:29 ` Brendan Tildesley via Bug reports for GNU Guix
2021-04-10 7:08 ` Pierre Neidhardt
2022-10-09 6:48 ` Brendan Tildesley
2022-10-10 12:22 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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=1448605157.72653.1617965795461@office.mailbox.org \
--to=bug-guix@gnu.org \
--cc=37955@debbugs.gnu.org \
--cc=btild@mailbox.org \
--cc=mail@ambrevar.xyz \
/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).