Fedora 41 insync repo failure [build + repo updated]

Bugs and issues Linux
23

I’ve gotten word that the build is going to be ready very soon. I know I’ve mentioned “soon” before and I can understand how frustrating it is to keep waiting, but rest assured that I am working closely with the Linux engineer to make sure this is available at the soonest possible time.

Thank you for your patience!

1 Like
24

Re: Dolphin plugin, there is no update yet but I’ll follow up on this one too.

25

Yeah, We are waitin, waiting and waiting.

26

And waiting and waiting and waiting…

27

Better that we wait, and that the build is good, than it be released too early with issues…

Thanks for the update @mia

1 Like
28

Hello, everyone.
I am successfully running Insync on my Fedora 41;
What did I do?
Temporarily until the offical version comes out.
I’m using the Fedora 40 version, with no repository errors.
I simply downloaded the “.rpm” from the website and installed it locally on my PC.
Then I edited the file in:
“/etc/yum.repos.d/insync.repo”
Replacing:
“baseurl=http://yum.insync.io/[DISTRIBUTION]/$releasever/”
For:
“baseurl=http://yum.insync.io/fedora/40/”
After that you can run “yum update” and everything will be working.
This is temporary, as soon as the updated version comes out, I’ll make the adjustments.
I hope this helps you.

1 Like
29

Thank you for sharing this workaround, @Willian_Armond!

30

There is no need to download the .rpm file - updating the insync.repo file suffices.

Thanks for the idea, @Willian_Armond

1 Like
31

just in case your installer uses Python 2 scripts: they are no longer supported in Fedora 41.

32

I had previously installed on a fresh Fedora 41 install with no issues other than the 404 repo load error. I have just updated my system, and the repo is live, and md has downloaded with no errors. Thanks @mia and the team.

33

I met the following error when I tried to update:

dnf update 
Updating and loading repositories:
Repositories loaded.
Package                  Arch    Version                  Repository        Size
Upgrading:
 insync                  x86_64  3.9.4.60020-fc41         insync       404.4 MiB
   replacing insync      x86_64  3.9.4.60020-fc40         insync       405.0 MiB

Transaction Summary:
 Upgrading:          1 package
 Replacing:          1 package

Total size of inbound packages is 158 MiB. Need to download 0 B.
Is this ok [y/N]: y
[1/1] insync-0:3.9.4.60020-fc41.x86_64  100% |   0.0   B/s |   0.0   B |  00m00s
>>> Already downloaded
--------------------------------------------------------------------------------
[1/1] Total                             100% |   0.0   B/s |   0.0   B |  00m01s
Running transaction
Transaction failed: Signature verification failed.
PGP check for package "insync-3.9.4.60020-fc41.x86_64" (/var/cache/libdnf5/insync-4a6229692cac8324/packages/insync-3.9.4.60020-fc41.x86_64.rpm) from repo "insync" has failed: Problem occurred when opening the package.
34

Hi everyone!

The Fedora 41 build is now available in our downloads page: https://www.insynchq.com/downloads/linux

Thank you for your patience!

35

@felipehw Hey! Just checking - can you let me know if this issue occurs from downloading and installing the build directly from https://www.insynchq.com/downloads/linux?

Mia

36

Installing the RPM directly work, as it bypass the signature verification.
So, please update the package with the correct signature.

2 Likes
37

The signature failure is:

error: Verifying a signature using certificate AEEB94E9C5A3B54ECFA4A66AA684470CACCAF35C (Insynchq Inc <services@insynchq.com>):
  1. Certificate A684470CACCAF35C invalid: certificate is not alive
      because: The primary key is not live
      because: Expired on 2024-09-08T06:24:38Z
  2. Key A684470CACCAF35C invalid: key is not alive
      because: The primary key is not live
      because: Expired on 2024-09-08T06:24:38Z
        package insync-3.9.4.60020-fc41.x86_64 does not verify: Header V4 RSA/SHA512 Signature, key ID accaf35c: NOTTRUSTED

Does the rpm come with a new sig, and we have to clear out the old key?

38

So, rpm -e gpg-pubkey-accaf35c-504d6503 does the trick: it removes the key with the old signature and allows the update to bring along the key with the new signature.

3 Likes
39

Thank you @MJG for sharing this!

40

Thanks @MJG! I confirm that removing the old key also works for me, but beware that the key extension may be invalid, so one should look for the first part ‘accaf35c’ and check that the corresponding key is the insync key: rpm -qi gpg-pubkey-accaf35c-5f587526 since the key on my machine had the extension 5f587526. When this key was removed sudo rpm -e gpg-pubkey-accaf35c-5f587526 the package for Fedora installed from the repository as it should.

2 Likes