GNU logs - #35801, boring messages

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#35801: 27.0.50; [w32] Corrupt ~/.emacs.d/elpa/gnupg/ causes Emacs startup failure with gnu-elpa-keyring-update installed (was Re: Investigating Emacs startup failure)
Resent-From: Richard Copley <rcopley@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Sun, 19 May 2019 19:29:01 +0000
Resent-Message-ID: <handler.35801.B.155829413216371 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 35801 <at> debbugs.gnu.org
MIME-Version: 1.0
From: Richard Copley <rcopley@HIDDEN>
Date: Sun, 19 May 2019 20:28:14 +0100
Message-ID: <CAPM58ohSW-WrOo6a1nMFnUnmLE1zFU9JT2rJH6PZU3O2jenqiw@HIDDEN>
Content-Type: multipart/alternative; boundary="00000000000073559f0589429f5d"
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

--00000000000073559f0589429f5d
Content-Type: text/plain; charset="UTF-8"

I got my Emacs into a state where it failed to start. I asked about it on
help-gnu-emacs[1]. I fixed my Emacs, but didn't get to the bottom of the
problem. Stefan asked me to make it a bug report: "such a corrupt directory
shouldn't prevent use of Emacs".

After installing "gnu-elpa-keyring-update-2019.3" from GNU ELPA, my Emacs
stopped working: when invoked as "emacs" from the command line, it printed
a message, then exited with status -1 without displaying a frame. The
message was:

GPG error: "no usable configuration", OpenPGP

Emacs started normally when invoked as "emacs -Q". Having done that, I
could load my init file with M-x load-file, and then everything looked
normal and there were no messages or errors.

I uninstalled all packages (the problem went away) and reinstalled them
one-by-one. The problem came back after installing
"gnu-elpa-keyring-update-2019.3".

I tried renaming .emacs.d/ to reproduce the problem, but could not. On a
hunch I deleted the gnupg/ directory in ~/.emacs.d/elpa before reinstalling
the "gnu-elpa-keyring-update-2019.3" package. This fixed the problem, but
also destroyed my means of reproducing it.

[1] https://lists.gnu.org/archive/html/help-gnu-emacs/2019-05/msg00418.html

In GNU Emacs 27.0.50 (build 1, x86_64-w64-mingw32)
 of 2019-05-19 built on MACHINE
Repository revision: b87e5eea1dd7c7345d0a9f82759eedfd7c9a8099
Repository branch: master
Windowing system distributor 'Microsoft Corp.', version 10.0.18890

Configured using:
 'configure --config-cache --with-modules --without-pop --without-dbus
 --without-gconf --without-gsettings CFLAGS=-O3'

Configured features:
XPM JPEG TIFF GIF PNG RSVG SOUND NOTIFY W32NOTIFY ACL GNUTLS LIBXML2
ZLIB TOOLKIT_SCROLL_BARS MODULES THREADS JSON PDUMPER LCMS2 GMP
Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.

Important settings:
  value of $LANG: ENG
  locale-coding-system: cp1252

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  global-eldoc-mode: t
  eldoc-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message rmc puny seq byte-opt gv
bytecomp byte-compile cconv dired dired-loaddefs format-spec rfc822 mml
easymenu mml-sec password-cache epa derived epg epg-config gnus-util
rmail rmail-loaddefs text-property-search time-date mm-decode mm-bodies
mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader cl-loaddefs
cl-lib sendmail rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mail-utils
elec-pair mule-util tooltip eldoc electric uniquify ediff-hook vc-hooks
lisp-float-type mwheel dos-w32 ls-lisp disp-table term/w32-win w32-win
w32-vars term/common-win tool-bar dnd fontset image regexp-opt fringe
tabulated-list replace newcomment text-mode elisp-mode lisp-mode
prog-mode register page menu-bar rfn-eshadow isearch timer select
scroll-bar mouse jit-lock font-lock syntax facemenu font-core
term/tty-colors frame cl-generic cham georgian utf-8-lang misc-lang
vietnamese tibetan thai tai-viet lao korean japanese eucjp-ms cp51932
hebrew greek romanian slovak czech european ethiopic indian cyrillic
chinese composite charscript charprop case-table epa-hook jka-cmpr-hook
help simple abbrev obarray minibuffer cl-preloaded nadvice loaddefs
button faces cus-face macroexp files text-properties overlay sha1 md5
base64 format env code-pages mule custom widget hashtable-print-readable
backquote threads w32notify w32 lcms2 multi-tty make-network-process
emacs)

Memory information:
((conses 16 45773 9549)
 (symbols 48 5970 1)
 (strings 32 16404 1855)
 (string-bytes 1 511709)
 (vectors 16 8836)
 (vector-slots 8 111332 13450)
 (floats 8 19 333)
 (intervals 56 217 15)
 (buffers 992 11))

--00000000000073559f0589429f5d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I got my Emacs into a state where it failed to start. I as=
ked about it on help-gnu-emacs[1]. I fixed my Emacs, but didn&#39;t get to =
the bottom of the problem. Stefan asked me to make it a bug report: &quot;s=
uch a corrupt directory shouldn&#39;t prevent use of Emacs&quot;.<br><br>Af=
ter installing &quot;gnu-elpa-keyring-update-2019.3&quot; from GNU ELPA, my=
 Emacs stopped working: when invoked as &quot;emacs&quot; from the command =
line, it printed a message, then exited with status -1 without displaying a=
 frame. The message was:<br><br>GPG error: &quot;no usable configuration&qu=
ot;, OpenPGP<br><br>Emacs started normally when invoked as &quot;emacs -Q&q=
uot;. Having done that, I could load my init file with M-x load-file, and t=
hen everything looked normal and there were no messages or errors.<br><br>I=
 uninstalled all packages (the problem went away) and reinstalled them one-=
by-one. The problem came back after installing &quot;gnu-elpa-keyring-updat=
e-2019.3&quot;.<br><br>I tried renaming .emacs.d/ to reproduce the problem,=
 but could not. On a hunch I deleted the gnupg/ directory in ~/.emacs.d/elp=
a before reinstalling the &quot;gnu-elpa-keyring-update-2019.3&quot; packag=
e. This fixed the problem, but also destroyed my means of reproducing it.<b=
r><div><br></div><div>
[1] <a href=3D"https://lists.gnu.org/archive/html/help-gnu-emacs/2019-05/ms=
g00418.html">https://lists.gnu.org/archive/html/help-gnu-emacs/2019-05/msg0=
0418.html</a>

</div><div><br></div><div></div>In GNU Emacs 27.0.50 (build 1, x86_64-w64-m=
ingw32)<br>=C2=A0of 2019-05-19 built on MACHINE<br>Repository revision: b87=
e5eea1dd7c7345d0a9f82759eedfd7c9a8099<br>Repository branch: master<br>Windo=
wing system distributor &#39;Microsoft Corp.&#39;, version 10.0.18890<br><b=
r>Configured using:<br>=C2=A0&#39;configure --config-cache --with-modules -=
-without-pop --without-dbus<br>=C2=A0--without-gconf --without-gsettings CF=
LAGS=3D-O3&#39;<br><br>Configured features:<br>XPM JPEG TIFF GIF PNG RSVG S=
OUND NOTIFY W32NOTIFY ACL GNUTLS LIBXML2<br>ZLIB TOOLKIT_SCROLL_BARS MODULE=
S THREADS JSON PDUMPER LCMS2 GMP<br>Recent messages:<br>For information abo=
ut GNU Emacs and the GNU system, type C-h C-a.<br><br>Important settings:<b=
r>=C2=A0 value of $LANG: ENG<br>=C2=A0 locale-coding-system: cp1252<br><br>=
Major mode: Lisp Interaction<br><br>Minor modes in effect:<br>=C2=A0 toolti=
p-mode: t<br>=C2=A0 global-eldoc-mode: t<br>=C2=A0 eldoc-mode: t<br>=C2=A0 =
electric-indent-mode: t<br>=C2=A0 mouse-wheel-mode: t<br>=C2=A0 tool-bar-mo=
de: t<br>=C2=A0 menu-bar-mode: t<br>=C2=A0 file-name-shadow-mode: t<br>=C2=
=A0 global-font-lock-mode: t<br>=C2=A0 font-lock-mode: t<br>=C2=A0 blink-cu=
rsor-mode: t<br>=C2=A0 auto-composition-mode: t<br>=C2=A0 auto-encryption-m=
ode: t<br>=C2=A0 auto-compression-mode: t<br>=C2=A0 line-number-mode: t<br>=
=C2=A0 transient-mark-mode: t<br><br>Load-path shadows:<br>None found.<br><=
br>Features:<br>(shadow sort mail-extr emacsbug message rmc puny seq byte-o=
pt gv<br>bytecomp byte-compile cconv dired dired-loaddefs format-spec rfc82=
2 mml<br>easymenu mml-sec password-cache epa derived epg epg-config gnus-ut=
il<br>rmail rmail-loaddefs text-property-search time-date mm-decode mm-bodi=
es<br>mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader cl-loadd=
efs<br>cl-lib sendmail rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mail-u=
tils<br>elec-pair mule-util tooltip eldoc electric uniquify ediff-hook vc-h=
ooks<br>lisp-float-type mwheel dos-w32 ls-lisp disp-table term/w32-win w32-=
win<br>w32-vars term/common-win tool-bar dnd fontset image regexp-opt fring=
e<br>tabulated-list replace newcomment text-mode elisp-mode lisp-mode<br>pr=
og-mode register page menu-bar rfn-eshadow isearch timer select<br>scroll-b=
ar mouse jit-lock font-lock syntax facemenu font-core<br>term/tty-colors fr=
ame cl-generic cham georgian utf-8-lang misc-lang<br>vietnamese tibetan tha=
i tai-viet lao korean japanese eucjp-ms cp51932<br>hebrew greek romanian sl=
ovak czech european ethiopic indian cyrillic<br>chinese composite charscrip=
t charprop case-table epa-hook jka-cmpr-hook<br>help simple abbrev obarray =
minibuffer cl-preloaded nadvice loaddefs<br>button faces cus-face macroexp =
files text-properties overlay sha1 md5<br>base64 format env code-pages mule=
 custom widget hashtable-print-readable<br>backquote threads w32notify w32 =
lcms2 multi-tty make-network-process<br>emacs)<br><br>Memory information:<b=
r>((conses 16 45773 9549)<br>=C2=A0(symbols 48 5970 1)<br>=C2=A0(strings 32=
 16404 1855)<br>=C2=A0(string-bytes 1 511709)<br>=C2=A0(vectors 16 8836)<br=
>=C2=A0(vector-slots 8 111332 13450)<br>=C2=A0(floats 8 19 333)<br>=C2=A0(i=
ntervals 56 217 15)<br>=C2=A0(buffers 992 11))<br></div>

--00000000000073559f0589429f5d--

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Richard Copley <rcopley@HIDDEN>
Subject: bug#35801: Acknowledgement (27.0.50; [w32] Corrupt
 ~/.emacs.d/elpa/gnupg/ causes Emacs startup failure with gnu-elpa-keyring-update
 installed (was Re: Investigating Emacs startup failure))
Message-ID: <handler.35801.B.155829413216371.ack <at> debbugs.gnu.org>
References: <CAPM58ohSW-WrOo6a1nMFnUnmLE1zFU9JT2rJH6PZU3O2jenqiw@HIDDEN>
X-Gnu-PR-Message: ack 35801
X-Gnu-PR-Package: emacs
Reply-To: 35801 <at> debbugs.gnu.org
Date: Sun, 19 May 2019 19:29:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-gnu-emacs@HIDDEN

If you wish to submit further information on this problem, please
send it to 35801 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
35801: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D35801
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#35801: 27.0.50; [w32] Corrupt ~/.emacs.d/elpa/gnupg/ causes Emacs startup failure with gnu-elpa-keyring-update installed (was Re: Investigating Emacs startup failure)
Resent-From: Eli Zaretskii <eliz@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Wed, 22 May 2019 06:43:02 +0000
Resent-Message-ID: <handler.35801.B35801.155850735126706 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Richard Copley <rcopley@HIDDEN>
Cc: 35801 <at> debbugs.gnu.org
Date: Wed, 22 May 2019 09:42:31 +0300
Message-Id: <83ef4r7zxk.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
In-reply-to: <CAPM58ohSW-WrOo6a1nMFnUnmLE1zFU9JT2rJH6PZU3O2jenqiw@HIDDEN>
 (message from Richard Copley on Sun, 19 May 2019 20:28:14 +0100)
References: <CAPM58ohSW-WrOo6a1nMFnUnmLE1zFU9JT2rJH6PZU3O2jenqiw@HIDDEN>
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

> From: Richard Copley <rcopley@HIDDEN>
> Date: Sun, 19 May 2019 20:28:14 +0100
> 
> I got my Emacs into a state where it failed to start. I asked about it on help-gnu-emacs[1]. I fixed my Emacs,
> but didn't get to the bottom of the problem. Stefan asked me to make it a bug report: "such a corrupt directory
> shouldn't prevent use of Emacs".
> 
> After installing "gnu-elpa-keyring-update-2019.3" from GNU ELPA, my Emacs stopped working: when invoked
> as "emacs" from the command line, it printed a message, then exited with status -1 without displaying a
> frame. The message was:
> 
> GPG error: "no usable configuration", OpenPGP
> 
> Emacs started normally when invoked as "emacs -Q". Having done that, I could load my init file with M-x
> load-file, and then everything looked normal and there were no messages or errors.
> 
> I uninstalled all packages (the problem went away) and reinstalled them one-by-one. The problem came back
> after installing "gnu-elpa-keyring-update-2019.3".
> 
> I tried renaming .emacs.d/ to reproduce the problem, but could not. On a hunch I deleted the gnupg/ directory
> in ~/.emacs.d/elpa before reinstalling the "gnu-elpa-keyring-update-2019.3" package. This fixed the problem,
> but also destroyed my means of reproducing it.

What would you suggest we do to make some progress with this bug
report?

Thanks.

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#35801: 27.0.50; [w32] Corrupt ~/.emacs.d/elpa/gnupg/ causes Emacs startup failure with gnu-elpa-keyring-update installed (was Re: Investigating Emacs startup failure)
Resent-From: Richard Copley <rcopley@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Wed, 22 May 2019 07:53:01 +0000
Resent-Message-ID: <handler.35801.B35801.15585115351699 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Eli Zaretskii <eliz@HIDDEN>
Cc: 35801 <at> debbugs.gnu.org
MIME-Version: 1.0
References: <CAPM58ohSW-WrOo6a1nMFnUnmLE1zFU9JT2rJH6PZU3O2jenqiw@HIDDEN>
 <83ef4r7zxk.fsf@HIDDEN>
In-Reply-To: <83ef4r7zxk.fsf@HIDDEN>
From: Richard Copley <rcopley@HIDDEN>
Date: Wed, 22 May 2019 08:51:40 +0100
Message-ID: <CAPM58ogNu9it6=x2Edj+rtH_t0hFKTLVnB-t_582W6c5yqfzYw@HIDDEN>
Content-Type: multipart/alternative; boundary="000000000000ede2bf0589753d0e"
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

--000000000000ede2bf0589753d0e
Content-Type: text/plain; charset="UTF-8"

On Wed, 22 May 2019 at 07:42, Eli Zaretskii <eliz@HIDDEN> wrote:

> > From: Richard Copley <rcopley@HIDDEN>
> > Date: Sun, 19 May 2019 20:28:14 +0100
> >
> > I got my Emacs into a state where it failed to start. I asked about it
> on help-gnu-emacs[1]. I fixed my Emacs,
> > but didn't get to the bottom of the problem. Stefan asked me to make it
> a bug report: "such a corrupt directory
> > shouldn't prevent use of Emacs".
> >
> > After installing "gnu-elpa-keyring-update-2019.3" from GNU ELPA, my
> Emacs stopped working: when invoked
> > as "emacs" from the command line, it printed a message, then exited with
> status -1 without displaying a
> > frame. The message was:
> >
> > GPG error: "no usable configuration", OpenPGP
> >
> > Emacs started normally when invoked as "emacs -Q". Having done that, I
> could load my init file with M-x
> > load-file, and then everything looked normal and there were no messages
> or errors.
> >
> > I uninstalled all packages (the problem went away) and reinstalled them
> one-by-one. The problem came back
> > after installing "gnu-elpa-keyring-update-2019.3".
> >
> > I tried renaming .emacs.d/ to reproduce the problem, but could not. On a
> hunch I deleted the gnupg/ directory
> > in ~/.emacs.d/elpa before reinstalling the
> "gnu-elpa-keyring-update-2019.3" package. This fixed the problem,
> > but also destroyed my means of reproducing it.
>
> What would you suggest we do to make some progress with this bug
> report?
>
> Thanks.
>

If the the bug is that errors during package quickstart prevent Emacs from
starting and can't easily be debugged, then it's easy to come up with a
recipe.
Customize and save package-enable-at-startup and package-quickstart to t,
run package-quickstart-refresh, edit package-quickstart.el and insert
(error "test"), then invoke emacs. It should echo "test" and exit with
status -1.
I hope that helps.
Thanks.

--000000000000ede2bf0589753d0e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Wed, 22 May 2019 at 07:42, Eli Zaretskii &lt;<a href=3D"mailto:el=
iz@HIDDEN">eliz@HIDDEN</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">&gt; From: Richard Copley &lt;<a href=3D"mailto:rco=
pley@HIDDEN" target=3D"_blank">rcopley@HIDDEN</a>&gt;<br>
&gt; Date: Sun, 19 May 2019 20:28:14 +0100<br>
&gt; <br>
&gt; I got my Emacs into a state where it failed to start. I asked about it=
 on help-gnu-emacs[1]. I fixed my Emacs,<br>
&gt; but didn&#39;t get to the bottom of the problem. Stefan asked me to ma=
ke it a bug report: &quot;such a corrupt directory<br>
&gt; shouldn&#39;t prevent use of Emacs&quot;.<br>
&gt; <br>
&gt; After installing &quot;gnu-elpa-keyring-update-2019.3&quot; from GNU E=
LPA, my Emacs stopped working: when invoked<br>
&gt; as &quot;emacs&quot; from the command line, it printed a message, then=
 exited with status -1 without displaying a<br>
&gt; frame. The message was:<br>
&gt; <br>
&gt; GPG error: &quot;no usable configuration&quot;, OpenPGP<br>
&gt; <br>
&gt; Emacs started normally when invoked as &quot;emacs -Q&quot;. Having do=
ne that, I could load my init file with M-x<br>
&gt; load-file, and then everything looked normal and there were no message=
s or errors.<br>
&gt; <br>
&gt; I uninstalled all packages (the problem went away) and reinstalled the=
m one-by-one. The problem came back<br>
&gt; after installing &quot;gnu-elpa-keyring-update-2019.3&quot;.<br>
&gt; <br>
&gt; I tried renaming .emacs.d/ to reproduce the problem, but could not. On=
 a hunch I deleted the gnupg/ directory<br>
&gt; in ~/.emacs.d/elpa before reinstalling the &quot;gnu-elpa-keyring-upda=
te-2019.3&quot; package. This fixed the problem,<br>
&gt; but also destroyed my means of reproducing it.<br>
<br>
What would you suggest we do to make some progress with this bug<br>
report?<br>
<br>
Thanks.<br></blockquote><div><br></div><div>
If the the bug is that errors during package quickstart prevent Emacs=20
from starting and can&#39;t easily be debugged, then it&#39;s easy to come =
up=20
with a recipe.<div class=3D"gmail_quote">Customize and save=20
package-enable-at-startup and package-quickstart to t, run=20
package-quickstart-refresh, edit package-quickstart.el and insert (error
 &quot;test&quot;), then invoke emacs. It should echo &quot;test&quot; and =
exit with status=20
-1.<br></div><div class=3D"gmail_quote">I hope that helps.</div><div class=
=3D"gmail_quote">Thanks.</div><br></div></div></div>

--000000000000ede2bf0589753d0e--

Message sent to bug-gnu-emacs@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#35801: 27.0.50; [w32] Corrupt ~/.emacs.d/elpa/gnupg/ causes Emacs startup failure with gnu-elpa-keyring-update installed (was Re: Investigating Emacs startup failure)
Resent-From: Eli Zaretskii <eliz@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Wed, 22 May 2019 08:35:02 +0000
Resent-Message-ID: <handler.35801.B35801.15585140756856 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 35801
X-GNU-PR-Package: emacs
X-GNU-PR-Keywords: 
To: Richard Copley <rcopley@HIDDEN>
Cc: 35801 <at> debbugs.gnu.org
Received: via spool by 35801-submit <at> debbugs.gnu.org id=B35801.15585140756856
          (code B ref 35801); Wed, 22 May 2019 08:35:02 +0000
Received: (at 35801) by debbugs.gnu.org; 22 May 2019 08:34:35 +0000
Received: from localhost ([127.0.0.1]:41543 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1hTMhm-0001mW-Ur
	for submit <at> debbugs.gnu.org; Wed, 22 May 2019 04:34:35 -0400
Received: from eggs.gnu.org ([209.51.188.92]:47355)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <eliz@HIDDEN>) id 1hTMhl-0001mK-S4
 for 35801 <at> debbugs.gnu.org; Wed, 22 May 2019 04:34:34 -0400
Received: from fencepost.gnu.org ([2001:470:142:3::e]:33830)
 by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <eliz@HIDDEN>)
 id 1hTMhe-0003N0-Gk; Wed, 22 May 2019 04:34:27 -0400
Received: from [176.228.60.248] (port=2265 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <eliz@HIDDEN>)
 id 1hTMhb-00072u-Uz; Wed, 22 May 2019 04:34:24 -0400
Date: Wed, 22 May 2019 11:34:30 +0300
Message-Id: <831s0q99bd.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
In-reply-to: <CAPM58ogNu9it6=x2Edj+rtH_t0hFKTLVnB-t_582W6c5yqfzYw@HIDDEN>
 (message from Richard Copley on Wed, 22 May 2019 08:51:40 +0100)
References: <CAPM58ohSW-WrOo6a1nMFnUnmLE1zFU9JT2rJH6PZU3O2jenqiw@HIDDEN>
 <83ef4r7zxk.fsf@HIDDEN>
 <CAPM58ogNu9it6=x2Edj+rtH_t0hFKTLVnB-t_582W6c5yqfzYw@HIDDEN>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Spam-Score: -2.3 (--)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -3.3 (---)

> From: Richard Copley <rcopley@HIDDEN>
> Date: Wed, 22 May 2019 08:51:40 +0100
> Cc: 35801 <at> debbugs.gnu.org
> 
> If the the bug is that errors during package quickstart prevent Emacs from starting and can't easily be
> debugged, then it's easy to come up with a recipe.
> Customize and save package-enable-at-startup and package-quickstart to t, run package-quickstart-refresh,
> edit package-quickstart.el and insert (error "test"), then invoke emacs. It should echo "test" and exit with status
> -1.

Thanks, if that's the problem, then I think it's clear.

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.