Slackpkg+ fatal errors with Ponce and SlackOnly repos
In the last weeks I'm experiencing some fatal errors when running slackpkg update. Of course, this happens only with slackpkg+ plugin for third party repositories.
The errors are: Code:
failed: Connection refused. Code:
2017-02-28 13:21:15 URL:http://ponce.cc/slackware/slackware-current/packages/CHECKSUMS.md5.asc [801/801] -> "/dev/shm/slackpkg.7WPTJN/CHECKSUMS.md5-ponce.asc" [1] Is anybody out there experiencing the same with those repositories? Does anyone know what happened to these repos? |
I just tried with the slackonly repository and yes, I get the same error.
|
It has been almost two months past from the OP and Ponce repo update still fails with:
Code:
!!! F A T A L !!! Code:
pub 2048R/ED123FBC 2011-01-01 |
Ponce's binary repository is not intended to be used with slackpkg+
it's just a collection of binary packages he provided without any metadata used by slackpkg+ please see the supported repositories |
Quote:
Now I realize my OP wasn't clear enough. Ponce's repo once worked fine with Slackpkg+, with no GPG key error of any sort. Since the OP it's not working that way anymore, as it looks that Ponce is not updating the signatures file anymore as he used to. I posted this here in the hope that 1) Ponce himself could see that or 2) if anyone reading this could warn him of this minor issue. I do not expect Slacpkg+ to support Ponce's repo. What I do expect is that Ponce could make it possible to me/us (the user/users) a package file integrity verification before install it. |
Code:
bash $ wget -q "http://ponce.cc/slackware/slackware-current/packages/CHECKSUMS.md5" "http://ponce.cc/slackware/slackware-current/packages/CHECKSUMS.md5.asc" Code:
https://pgp.mit.edu/ |
hi deny,
the last key you show it's not mine: the GPG-KEY present in the 32bit repo (the 64bit is ok) is actually an old one that got there when I reinstalled the vm where I build packages, it will be fixed soon, thanks. Code:
$ gpg --with-fingerprint GPG-KEY Code:
$ gpg --with-fingerprint GPG-KEY I don't have time to support the repositories, those are just the packages I use on my installations and they're given away with no warranties. |
Quote:
I apologize on confusing you with another one, but you were wight right as I had your old key in place (2048R/36287643). Now that I updated it properly (4096R/02BEF947), all runs fine again. Just so you know, your old key is still listed at hkps.pool.sks-keyservers.net, but the new one is not. |
All times are GMT -5. The time now is 06:20 AM. |