On Wed, 20 Jul 2022 at 16:12, Dan Čermák <dan.cermak@cgc-instruments.com> wrote:
Hi Kevin and all,

"Kevin P. Fleming" <kpfleming@redhat.com> writes:

> On 7/20/22 14:57, Marcus Müller wrote:
>> Oh! That comes as a surprise. Let me try a rebuild!
>>
>> :( I was really looking forward to emacs-pgtk.
>>
> Forgive my relative newbie-ness here, but this proposal is to upgrade
> Emacs to version 28 in F37. That seems fine.
>
> This week my F36 system got upgraded to Emacs version 28, so it's
> already in F36. How is that possible?

Apologies, this is my fault. After the Emacs 28 PR got merged, I went
ahead, built Emacs in Fedora 36 as well and submitted it as an
update [1] (after one borked attempt before), which got quickly pushed
to stable.

Sorry for breaking your packages Jerry. Maybe we should add some gating
tests to prevent this kind of breakage in the future. Would you have
some details what happened?


I have seen a couple of reports about emacs not starting after update with the message:

```
Cannot open load file: No such file or directory, comp
```

Removing the users .emacs/.emacs.d does not change anything so I am guessing there is some other 'breakage'. What can be done to debug this?


--
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren