Latest emacs build is blocked due to "missing publisher"

[pank]

Sorry, this is related to https://github.com/kiennq/emacs-build/ but that repo has no issue tracker. This repo seemed somewhat related...

I use your emacs builds on my PC. They are great so thanks! I can't build on my windows PC and I don't have an admin account.

Something happened with the latest version and it gets blocked. Windows claims it does not have a published, but it's probably something else (I don't see a published for the previous version either...).

This version is blocked on my PC.

The version from ‎19 ‎September ‎2023 works, I guess this one, works well.

Sorry again for using the wrong issue tracker.

[kiennq]

It's working for me though. Can you try the latest one to see if it's working for you? The exe is built by Github action so it should be safe, if you check the hash is the same as the one in the scoop then I guess you can probably allow it to run.

[pank]

I downloaded the latest release. Still the same.

I probably have a more locked-down windows environment than most. I don't have admin rights and I cannot allow or disallow something to run. But the version that was probably compiled on Sep. 14 works. I think it is this one.

Could the change in the build setup have changed something about exe signatures? I.e. this:

      - name: Setup Msys2
        uses: msys2/setup-msys2@v2
        if: runner.os == 'Windows'
        with:
          msystem: UCRT64
          update: true
          release: false

Was UCRT64 used before?

For now, it seems that copying over runemacs.exe from the old installation makes it run...

[pank]

Aside and almost totally unrelated.

Since a while, the lisp/leim/quail folder has been missing from the package. Apparently it's part of the slim packaging.

This breaks set-input-method, toggle-input-method and activate-transient-input-method. The folder is less than a mb.

[kiennq]

Aside and almost totally unrelated.

Since a while, the lisp/leim/quail folder has been missing from the package. Apparently it's part of the slim packaging.

This breaks set-input-method, toggle-input-method and activate-transient-input-method. The folder is less than a mb.

Yeah, I intentionally omit that one as I think we should use Windows's input method instead of uncompleted support in Emacs. The leim folder is around 20MB ish and cutting it will trim down Emacs a bit.

[kiennq]

Was UCRT64 used before?

The UCRT64 is using the new ucrt version of stdlibc++ instead of the old msvcrt. This is the recommendation now so I would like to keep it. Btw, I've submitted the runemacs to MS malware asking for a rescan and unblock from smartscreen, let's see if that will resolve your issue

[pank]

Yeah, I intentionally omit that one as I think we should use Windows's input method instead of uncompleted support in Emacs. The leim folder is around 20MB ish and cutting it will trim down Emacs a bit.

I just like the TeX input method as it's the quickest way to write unicode math. I don't know much about what it possible with windows input methods. Never checked.

Re size: I just looked at the numbers on the savannah and summed them up (829084) and assumed they were bytes and that they wouldn't change much during compilation. But I didn't check after compilation sizes.

[pank]

The UCRT64 is using the new ucrt version of stdlibc++ instead of the old msvcrt. This is the recommendation now so I would like to keep it.

This seems reasonable.

Btw, I've submitted the runemacs to MS malware asking for a rescan and unblock from smartscreen, let's see if that will resolve your issue

There must be some magic metadata missing and I guess that could be it...

[pank]

Turns out that you can make it work by calling the powershell command unblock-file on the exe files.

[kiennq]

Thank you, I will close this issue then,