Fedora 38 will be released on Tuesday, April 18. While the current F37 version works on F38, people are once again going to be getting repository errors, etc. when they update. Can we get this issue fixed? Seems every time there is a new release I have to write a nag note.
1 Like
Fedora 38 was released today, but I cannot upgrade as I get Insync errors. I hope that you are able to update the repository soon. I know Insync is not working on a Flatpak right now, but if there were a Flatpak, we would not have any problems any longer when a new Fedora (or other distribution) releases.
1 Like
Yeah, I don’t get why this is so hard, but it has been going on for years. To workaround, you can edit your insync.repo as follows:
#baseurl=http://yum.insync.io/fedora/$releasever/
baseurl=https://yum.insync.io/fedora/37/
Unfortunately, there is a new upgrade but it hasn’t been correctly signed, so you’ll get the following error until they fix:
GPG key at https://d2t3ff60b2tol4.cloudfront.net/repomd.xml.key (0xACCAF35C) is already installed
The GPG keys listed for the “insync repo” repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository… Failing package is: insync-3.8.5.50499-fc37.x86_64
GPG Keys are configured as: https://d2t3ff60b2tol4.cloudfront.net/repomd.xml.key
Before I saw your reply I decided to play around with insync headless. I have set it up in a toolbox on Fedora Kinoite. Honestly, I will probably just use this from now on since I don’t need the gui and I don’t really like doing rpm-ostree overlays if I can help it. It seems to work well enough. Thanks.
Hi everyone! The Fedora 38 build has been added to our downloads page & repositories. Thank you for your patience!
Thank you very much! 
But still getting this error:
GPG key at https://d2t3ff60b2tol4.cloudfront.net/repomd.xml.key (0xACCAF35C) is already installed
The GPG keys listed for the “insync repo” repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository… Failing package is: insync-3.8.5.50499-fc38.x86_64
GPG Keys are configured as: https://d2t3ff60b2tol4.cloudfront.net/repomd.xml.key
1 Like
Hello and thank you for bringing this to my attention! Checking with our Linux Team what’s going on so we can address this accordingly 
Thanks for the quick response!
The command I am using is “dnf upgrade”, here is the output:
Dependencies resolved.
Package Architecture Version Repository Size
Upgrading:
insync x86_64 3.8.5.50499-fc38 insync 137 M
Transaction Summary
Upgrade 1 Package
Total download size: 137 M
Is this ok [y/N]: y
Downloading Packages:
insync-3.8.5.50499-fc38.x86_64.rpm 57 MB/s | 137 MB 00:02
Total 57 MB/s | 137 MB 00:02
insync repo 4.0 kB/s | 965 B 00:00
GPG key at https://d2t3ff60b2tol4.cloudfront.net/repomd.xml.key (0xACCAF35C) is already installed
The GPG keys listed for the “insync repo” repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository… Failing package is: insync-3.8.5.50499-fc38.x86_64
GPG Keys are configured as: https://d2t3ff60b2tol4.cloudfront.net/repomd.xml.key
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘dnf clean packages’.
Error: GPG check FAILED
Hi @gbcox
Do you have a different version of Insync currently installed? If yes, could you uninstall that version and then do sudo dnf install insync? Also maybe try clearing the cache sudo dnf clean all.
What are the contents of the insync.repo file?
What is the output of curl "https://d2t3ff60b2tol4.cloudfront.net/repomd.xml.key" | sha256sum?
The problem is that the current key referenced in the repo file is different than the key that was used to sign.
rpm -q --qf ‘%{NAME}-%{VERSION}-%{RELEASE} %{SIGPGP:pgpsig} %{SIGGPG:pgpsig}\n’ -p insync-3.8.5.50499-fc38.x86_64.rpm
warning: insync-3.8.5.50499-fc38.x86_64.rpm: Header V4 RSA/SHA512 Signature, key ID accaf35c: NOTTRUSTED
insync-3.8.5.50499-fc38 RSA/SHA512, Thu Apr 20 06:27:27 2023, Key ID a684470caccaf35c (none)
You either made a mistake and signed with the wrong key, OR you decided to change the key and didn’t update properly the key on cloudfront.
curl “https://d2t3ff60b2tol4.cloudfront.net/repomd.xml.key” | sha256sum
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 965 100 965 0 0 5545 0 --:–:-- --:–:-- --:–:-- 5578
761fa06d06484eddf785d718efdce14033bfa20de78d644d5153d2ca76f5b378 -
Here is my repo file:
[insync]
name=insync repo
baseurl=http://yum.insync.io/fedora/$releasever/
gpgcheck=1
gpgkey=https://d2t3ff60b2tol4.cloudfront.net/repomd.xml.key
enabled=1
metadata_expire=120m
Hi @gbcox
The signature in our package seems to be correct on our system.
From your output it seems like our key isn’t trusted:
warning: insync-3.8.5.50499-fc38.x86_64.rpm: Header V4 RSA/SHA512 Signature, key ID accaf35c: NOTTRUSTED
Or maybe perhaps your system has our expired key imported?
What’s the output of rpm -qi "gpg-pubkey-accaf35c"?
Thanks for the quick response… Here is the output:
rpm -qi “gpg-pubkey-accaf35c”
Name : gpg-pubkey
Version : accaf35c
Release : 57d58c01
Architecture: (none)
Install Date: Wed 22 Nov 2017 10:22:32 AM PST
Group : Public Keys
Size : 0
License : pubkey
Signature : (none)
Source RPM : (none)
Build Date : Sun 11 Sep 2016 09:53:21 AM PDT
Build Host : localhost
Packager : Insynchq Inc services@insynchq.com
Summary : gpg(Insynchq Inc services@insynchq.com)
Description :
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: rpm-4.14.0 (NSS-3)
mQENBFBNZQMBCADhvMmAAuYnB1rxzvGzz3rdYDT9pg6QCSI7gqTrimVS+SqkTVnj
Qh+ot849Vgfww50FMsNVTMX3QZVjJ/8/LrlZRLoiowBp9emH+Cvpmc+jjsBZJeuB
Urd2WzG1FZ1fx821UHmN8xr6JYq1ppuA9am5eI8ks2nGnc5UssEUWGWEnXcR4Q1y
AdcB1WvCz7GTEkQkf+aDJS3mbLp9nEMNd4C/U9B60Jp5Yerm+eaZL296VvSodQ2l
croqkbXZumsdVYE4FZJf88FKVXJc4QHpeMlJ0OVI+1cDXoFlGTlxkh6ofa27w1UR
2Fz70nf+fYxwnAFHL4irkIlsO/Rt8qodb1dBABEBAAG0JEluc3luY2hxIEluYyA8
c2VydmljZXNAaW5zeW5jaHEuY29tPokBPQQTAQIAJwIbLwIeAQIXgAULCQgHAwUV
CgkICwUWAgMBAAUCV9WMAQUJDwz08AAKCRCmhEcMrMrzXMOCB/0fIpEXsMfnLD/v
xJY544ltSRl4ioPCxd2t1CVn/9IFxFekLwahjpp25tIadoNBEeQZKTmxTEpFsHZv
HCvCoR0oy7ke3zJJlgpZtDDqJ8B3dK3eQQMti7CC6EKybHL4cms73LOz3qcryhgG
0AHzc5/XLKfJTPQJ2G03mNDjRhY+FAqBKuUNYllBJ2+4xE4no/lPoOPCEik+BeUx
fcT1lT+10FQJstbbuPZOwnfSHt4zj/GQ3SfnnSdgE3xwoUqmNqeFovHfPO0R5tS9
A/ZHH849CDlr38wJc3l0d2HjnP7+TzyBoO79p1X+DEBkHHkoR66sL33LXuVigyMt
Yj/kpWy2uQENBFBNZQMBCADJks7on83NVWcI0Y0PqUCihZG+XtYfv6w7gHWKgBk0
k/poiMKH/PzmxN1ncRxLBeysD11TQunKzfJpGN4GVQ6cb88fynHADwZ6Jyb9Umok
TXfz4fXIAaDo2/iQtsB5E7hlsLxhJDTVVdm1AiVWjLmBeCMCC0UP05K1RBCtnHTN
PBblvQFzv1T5vymDif4/b9Q5BO4SL9o9/IZrCaxz/EIJ3pp47YXDPFv9ZkUSPXGN
RLwLrJdrCz849AHozM0WWg/TDw8UY0WOhGn79n4torDY4R4t5ljgdRvyIo3N8czL
+/A51DEPKu2LtTbErwQC6tryx+x+ut9AD8O1TMynBlU1ABEBAAGJAkQEGAECAA8C
Gy4FAlfVkIIFCQ8M+XkBKcBdIAQZAQIABgUCUE1lAwAKCRAGu9wmAt/n50cEB/9I
95+eifdHcQmeEgDPKX19aWKmfPZFyYA31mJZkviwjCzE7+SqVH2qYYvzTjq6q7xw
sm1YifybChUs87iv5ek1Tdzi44k/GM1A7yryvwNBQAlw86Y6Q3pTRa+mpHnvpjo8
7C6rMknbX7kT5LwYzjz6dEIhy0odlBRktZLlDgPo2ue3x5yh0iDhfK8sByUQykMn
7rvgd4odeEl/WVTFmK5T6XQoXNDovlbsq21q0nPeTwb488a4X9XowT4JkOUaliaV
w8ntG+mE9YsJoxXqJXuOit4ILTPNxbNA81qOKTBuZYdaX7URw3WLrLI5SHEOju+E
YzDlKJ4JDyetm6Z20CspCRCmhEcMrMrzXCRJCACm0Ri93g6K1WB1FpcDIj0UU1/8
Z9XGT83WWaHfd6Bp2xVNyFOUo9QnMZmRUZVf64feYeUvoZnR0zcFofvLvY8bMCZY
Scn/rTPw8V6wraZsFxsIE96B5d1IfCDPxb8MGEG27Dm6WjEg65JeyeU9K7un4hyK
4jhjvYeKAVDG4PEAfrvLBiYc0TlSwPqhhnVB3uvEHZwpfBjobFGgaPTnYBEjXeql
6+QhJqHQrUGbfWDzyuVv8FuEzMNW0PTvZEEpeOdFHRqOo6My7erDprr/dzegyFvs
VqdHWsArPrPM102WLHgeooXihxqgDqg4KheAr1sHeGnTVG0Ow7E9RWg2ZUqF
=tmcY
-----END PGP PUBLIC KEY BLOCK-----
Hi @gbcox
It seems like your system has our expired key.
Can you remove it by doing sudo rpm -e gpg-pubkey-accaf35c-57d58c01 and then importing our new key sudo rpm --import https://d2t3ff60b2tol4.cloudfront.net/repomd.xml.key?
Let us know if it installs for you now
Thanks, that worked. Weird how that happened. I’ve been using insync for years and not sure how that occurred.
1 Like