Your message dated Thu, 08 Apr 2021 13:44:20 +0200
with message-id <87pmz5vw4r....@posteo.net>
and subject line Re: Bug#986553: Acknowledgement (emacs: make-closure is
undefined)
has caused the Debian Bug report #986553,
regarding emacs: make-closure is undefined
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
986553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs
Version: 1:27.1+1-3.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968)
(ignored: LC_ALL set to C), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages emacs depends on:
ii emacs-lucid 1:27.1+1-3.1
emacs recommends no packages.
emacs suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Now this might be embarrassing, but it turns out that the issue was I
was trying to evaluate bytecode compiled by Emacs 28, which I was just
working on.
The fact that Emacs 27 was broken just after the update while 28 was
working lead me to believe that there was an issue with the build. After
removing all the .elc files everything was fixed.
era <era+deb...@iki.fi> writes:
> On Wed, Apr 7, 2021, at 14:05, Philip Kaludercic wrote:
>> I apologize for the empty form, this was the first time I used
>> reportbug. I hope it is ok if I answer the question in this message.
>
> That's fine, but please still fill us in on what exactly failed.
>
> If you get a *Backtrace* buffer, please save it into a text file and
> send the file as an attachment to the bug report's address (the
> address in the Cc: header of this message).
>
> If this is related to something in your personal configuration, please
> also send relevant configuration file(s). Ideally, trim the file down
> to a minimal example which reliably reproduces the problem every time,
> and doesn't contain any unrelated configuration details.
>
> If you can't do that, please at least tell us whether the problem goes away
> with emacs -Q
>
> If this is specific to a configuration detail which isn't part of the
> default configuration, I would expect the priority of this bug to be
> reduced to regular or minor. I'll leave that to the package maintainer
> to decide, though.
--
Philip K.
--- End Message ---
