Page: Previous  1, 2

techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4126
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
You can use the add key ring manually by just supplying the key, I've done that for opera updates now and then.

Then you can just post the key and the command to add it.

For opera it was:

:: Code ::
wget -qO - http://deb.opera.com/archive.key | sudo apt-key add -

Back to top
DeepDayze
Status: Contributor
Joined: 21 May 2009
Posts: 128
Reply Quote
SO is it ever a good idea to DOWNGRADE apt?

OK thanks damentz, got your new key installed...what a pita and it will surely be an issue for those who have not updated. Looks like the only way now to install some unsigned package is to manually download and install then finding any dependencies as well (if there's dependencies that need to be met to install such package), at least till the 3rd party repo's owner issues an updated key that meets Debian's standards.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4126
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
no, all that's required is the apt-key file, a url, and the command.

Or downloading the deb and installing it manually.

Is unfortunate that debian failed to think this part through, clearly a new key should not require the new key to install it, lol.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1122
Reply Quote
So, I just did some testing - this only affects existing users, not new (ironically). If you are a new user you will get this output and apt-get will still allow you to install packages from the repository:

:: Code ::
W: GPG error: https://liquorix.net/debian sid InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9AE4078033F8024D
W: The repository 'http://liquorix.net/debian sid InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: There is no public key available for the following key IDs:
9AE4078033F8024D


However, if you get the message, E: Failed to fetch, for liquorix.net, you will need to run this command to make apt-get forget it ever knew liquorix.net existed:

:: Code ::
find /var/lib/apt/lists -name '*liquorix*' -exec sudo rm -fv {} \;


This will remove all cached lists of liquorix.net's contents. Then, the next time you run apt-get update, you'll get the message above that new users get, allowing you to run, apt-get install liquorix-keyring. It looks like the instructions on the homepage don't need to change, but any existing user running into this problem hopefully finds this thread. I'll sticky it so current subscribers to this repo can find the answer.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4126
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
:: Code ::
Get:5 https://liquorix.net/debian sid InRelease [7,339 B]                 
Ign:5 https://liquorix.net/debian sid InRelease
Get:6 https://liquorix.net/debian sid/main amd64 Packages [4,371 B]
Fetched 11.7 kB in 1s (8,755 B/s)
Reading package lists... Done
W: GPG error: https://liquorix.net/debian sid InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9AE4078033F8024D
W: The repository 'http://liquorix.net/debian sid InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: There is no public key available for the following key IDs:


I don't know what changed, but I am getting errors again on your repos, and can't install your kernels. I already ran the find rm thing, updated, installed liquorix-keyring, and anything else that seems related, but it's still broken.

When I try to install the kernels it just errors out during the install.

To be clear, the above answer is NOT working, it did work for a while, but it's not working now, and it was working before on this machine.

This isn't happening with other repos, what's going on? It shouldn't be this complicated to do a simple kernel install.

Remembering my windows days, I tried: apt-get remove --purge liquorix-keyring then apt-get get install liquorix-keyring then apt-get update again, and, the 3rd time, it finally worked without error.

There's obviously a packaging error of some type, but I can't tell you what it is.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1122
Reply Quote
That's odd, I tested this scenario specifically and it just worked. Since this is a one time thing and should never happen again, I'll leave the keyring directions as is - I think your installation must have had something funky going on with it.
Back to top
Licaon_kter
Status: Interested
Joined: 06 Aug 2010
Posts: 33
Location: Between the keyboard and the chair.
Reply Quote
Your Let's Encrypt cert for liquorix.net has expired on Apr 23, is that at fault too?
Back to top
zika
Status: Interested
Joined: 02 Apr 2012
Posts: 28
Reply Quote
:: Code ::
W: Failed to fetch http://liquorix.net/debian/dists/sid/future/binary*/Packages  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1122
Reply Quote
This was fixed yesterday, I need to configure the lets encrypt tools to renew automatically, that's not been done yet.
Back to top
Display posts from previous:   
Page: Previous  1, 2
All times are GMT - 8 Hours