Skip to content

Instantly share code, notes, and snippets.

@anshprat
Created March 18, 2016 00:26
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save anshprat/7993c5c06dbffe4f4980 to your computer and use it in GitHub Desktop.
Save anshprat/7993c5c06dbffe4f4980 to your computer and use it in GitHub Desktop.
unsigned slack
[root@mouthwa log]# sudo dnf update slack
slack 4.6 kB/s | 21 kB 00:04
Last metadata expiration check performed 0:00:00 ago on Fri Mar 18 05:52:27 2016.
Dependencies resolved.
======================================================================================================================================================
Package Arch Version Repository Size
======================================================================================================================================================
Upgrading:
slack x86_64 2.0.1-0.1.fc21 slack 46 M
Transaction Summary
======================================================================================================================================================
Upgrade 1 Package
Total download size: 46 M
Is this ok [y/N]: y
Downloading Packages:
slack-2.0.1-0.1.fc21.x86_64.rpm 988 kB/s | 46 MB 00:47
------------------------------------------------------------------------------------------------------------------------------------------------------
Total 988 kB/s | 46 MB 00:47
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Package slack-2.0.1-0.1.fc21.x86_64.rpm is not signed
@giacecco
Copy link

Same problem here, but for the first time today. Do you know what the problem is? Thanks.

@GoodMirek
Copy link

+1

Copy link

ghost commented May 27, 2016

sudo dnf update --nogpgcheck slack

@MarkieMark
Copy link

even better = more secure
while waiting for slack to sign packages

$ sudo dnf update --disablerepo=slack

@GoodMirek
Copy link

Seems Slack will never sign their packages, although their support promised that.
Difficult to believe in a company which finds it hard to just sign their product.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment