From: Eli Zaretskii <eliz@gnu.org>
To: Mirko Vukovic <mirko.vukovic@gmail.com>
Cc: 42984@debbugs.gnu.org, stefan@marxist.se
Subject: bug#42984: 27.1; package-list results in error while updating archive due to malformed path
Date: Thu, 26 Nov 2020 17:38:08 +0200 [thread overview]
Message-ID: <838saoqgbj.fsf@gnu.org> (raw)
In-Reply-To: <CAO73BAD4ByLJcrBzzmiwN0pMg6sGvQP9mmtT2RTkq6mRrLfC9Q@mail.gmail.com> (message from Mirko Vukovic on Thu, 26 Nov 2020 10:28:17 -0500)
> From: Mirko Vukovic <mirko.vukovic@gmail.com>
> Date: Thu, 26 Nov 2020 10:28:17 -0500
> Cc: Stefan Kangas <stefan@marxist.se>, 42984@debbugs.gnu.org
>
> Tracing package--check-signature-content
>
> * I trace it in plain emacs, started with emacs -Q
> * I edebug the function and step through it
> * I have a single signature and its status is no-pub-key which triggers the No public key error
>
> * This results in the message in the error buffer with the malformed directory
>
> Below is the code annotated with values of key variables. I did not see anything obvious.
>
> I evaluated context at several points. I following deeper into the epg-... functions, stopped when I saw
> compiler macros. I would need guidance to trace those.
Thanks. I think the situation is clear:
> ;; #s(epg-context :protocol OpenPGP :program "c:/msys64-a/usr/bin/gpg.exe"
The "C:/msys64-a" part indicates that gpg.exe is an MSYS2 port, not a
native MinGW port. So it's expected that it will manipulate
Posix-like file names like /c/foo/bar and /home/977315/... It is also
expected that it may not realize that "c:/foo/bar" is an absolute file
name, since in the Posix world any file name which doesn't begin with
a slash is not an absolute file name. So it concatenates the file
name passed to it by Emacs with /home/977315/... on the assumption
that the file name passed by Emacs is a relative file name.
Bottom line: you need to install a native MinGW port of gpg, or make
some wrapper script for gpg which would convert Windows d:/foo/bar
file names into the Posix-like format expected by MSYS2 executables.
Thanks.
next prev parent reply other threads:[~2020-11-26 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 14:06 bug#42984: 27.1; package-list results in error while updating archive due to malformed path Mirko Vukovic
2020-11-25 9:32 ` Stefan Kangas
[not found] ` <CAO73BABFZO6wpqGLmgRL_Tp8W6tG4cRYU-_9zoGEFCdOx+jhMA@mail.gmail.com>
2020-11-25 21:06 ` Stefan Kangas
2020-11-26 3:31 ` Eli Zaretskii
2020-11-26 4:36 ` Stefan Kangas
2020-11-26 14:09 ` Eli Zaretskii
2020-11-26 15:28 ` Mirko Vukovic
2020-11-26 15:38 ` Eli Zaretskii [this message]
2020-11-26 15:58 ` Mirko Vukovic
2020-11-26 16:36 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838saoqgbj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42984@debbugs.gnu.org \
--cc=mirko.vukovic@gmail.com \
--cc=stefan@marxist.se \
/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/emacs.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).