Sublime Forum

Unable to Install Sublime text or merge on Fedora 43

#1

We are unable to “normally” install sublime text or merge. Any attempt to normally install results in

Running transaction
Transaction failed: Rpm transaction failed.
  - package sublime-text-4200-1.x86_64 does not verify: no digest

There was another post which covered the topic well, here is the link.
https://forum.sublimetext.com/t/installation-in-fedora-43-not-possible/77387

I also checked the rpm package using rpm -Kv and I get this.

sublime-text-4200-1.x86_64.rpm:
    Header OpenPGP V4 RSA/SHA256 signature, key fingerprint: 1b64279675a4299dcfc70858ca464a9a222d23d0: OK
    Header SHA3-256 digest: NOTFOUND
    Header SHA256 digest: NOTFOUND
    Header SHA1 digest: NOTFOUND
    Payload SHA256 digest: NOTFOUND
    Payload SHA256 ALT digest: NOTFOUND
    Payload SHA3-256 digest: NOTFOUND
    Payload SHA3-256 ALT digest: NOTFOUND
    Payload SHA512 digest: NOTFOUND
    Payload SHA512 ALT digest: NOTFOUND
    Legacy OpenPGP V4 RSA/SHA256 signature, key fingerprint: 1b64279675a4299dcfc70858ca464a9a222d23d0: OK
    Legacy MD5 digest: NOTFOUND

Technically one could install with --nodigest flag, but its not recommended.

1 Like
#2

Hopefully, the issue could be fixed soon. Till then I’ll use the local RPM installation.

0 Likes
#3

This has been fixed now, though you’ll need to add the new key by following the instructions here: https://www.sublimetext.com/docs/linux_repositories.html

0 Likes
#4

I am still getting the same error. Is there something I am doing wrong? I removed the old repo, from /etc/yum.repos.d/ and followed the instructions on the site.

Package                         Arch     Version                         Repository             Size
Installing:
 sublime-text                   x86_64   4200-1                          sublime-text       51.8 MiB

Transaction Summary:
 Installing:         1 package

Total size of inbound packages is 20 MiB. Need to download 0 B.
After this operation, 52 MiB extra will be used (install 52 MiB, remove 0 B).
Is this ok [y/N]: y
[1/1] sublime-text-0:4200-1.x86_64                          100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded                                                                              
----------------------------------------------------------------------------------------------------
[1/1] Total                                                 100% |   0.0   B/s |   0.0   B |  00m00s
Running transaction
Transaction failed: Rpm transaction failed.
  - package sublime-text-4200-1.x86_64 does not verify: no digest

when I check rpmkeys -l I notice that, there are multiple sublime keys and the old key is still there.

1edde2cdfc025d17f6da9ec0adae6ad28a8f901a Sublime HQ Pty Ltd <support@sublimetext.com> public key
1b64279675a4299dcfc70858ca464a9a222d23d0 Sublime HQ Pty Ltd <support@sublimetext.com> public key 
ebc733b78aab352dc773bf857fe2fa12cf6e38f2 Sublime HQ Pty Ltd <support@sublimetext.com> public key

I don’t know if this is intended behavior, but I am still getting the installation error.

Thanks for assistance

0 Likes
#5

It still does’t work, I placed message above showing the error.
https://forum.sublimetext.com/t/unable-to-install-sublime-text-or-merge-on-fedora-43/77440/4?u=subfrostz

when I check the package digest is still NOTFOUND

15:03:45 ~/Downloads → rpm -Kv sublime-text-4200-1.x86_64.rpm 
sublime-text-4200-1.x86_64.rpm:
    Header OpenPGP V4 RSA/SHA256 signature, key fingerprint: 1b64279675a4299dcfc70858ca464a9a222d23d0: OK
    Header SHA3-256 digest: NOTFOUND
    Header SHA256 digest: NOTFOUND
    Header SHA1 digest: NOTFOUND
    Payload SHA256 digest: NOTFOUND
    Payload SHA256 ALT digest: NOTFOUND
    Payload SHA3-256 digest: NOTFOUND
    Payload SHA3-256 ALT digest: NOTFOUND
    Payload SHA512 digest: NOTFOUND
    Payload SHA512 ALT digest: NOTFOUND
    Legacy OpenPGP V4 RSA/SHA256 signature, key fingerprint: 1b64279675a4299dcfc70858ca464a9a222d23d0: OK
    Legacy MD5 digest: NOTFOUND
15:03:49 ~/Downloads →

Once again thanks for the assistance.

0 Likes
#6

That’s unfortunate. It looks like the version of rpm we’re using will only using a sha-1 digest, so we’ll need to do some infrastructure upgrades before that starts working.

0 Likes
#7

That makes sense. I believe there was changes made to signing since rpm v6.0. I’ll use something else in the mean time. Will there be a time table, or notification when the problem is fixed?

thanks for the help

0 Likes
#8

You can follow this issue: https://github.com/sublimehq/sublime_text/issues/6669

0 Likes