-
-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
W: GPG error: http://debian.yacy.net ./ Release: The following signatures were invalid: 8BD752501CB62448A30EA3EA1F968B3903D886E7 #124
Comments
Edit 1: Missing HTTPS also at the startpage, for example the links to download Edit 2: Wanted to register an account in the YaCy Wiki to edit the entries but my registration was refused so someone else must do this :) |
I also have the problem since upgrading from Debian Jessie to Stretch. It looks like these points will require some action from @Orbiter |
Same here. Is anyone ever going to fix this??? |
As an alternative I've set up a Debian repository on JFrog Bintray to distribute YaCy developer releases (including recent changes made after the latest stable official 1.92/9000 release). With the following steps (as root or with sudo) you should be able to install a recent YaCy version (1.921.9232 when writing this) without error on a Debian Stretch :
Note for an eventual upgrade from YaCy 1.92/9000 : authentication method changed from Basic HTTP to Digest HTTP (see default configuration file /usr/share/yacy/defaults/web.xml). This makes the password encoding different : so when upgrading from YaCY version 1.92.9000 or lower, please run 'dpkg-reconfigure yacy' after the upgrade to enter again and thus re-encode your YaCy administrator password. Feedback will be welcome! |
Thanks! Will take a look at it, when I find the time and quiet... |
I uninstalled the package and installed the current 1.92/9000 build for Linux from the tarball on yacy.net, and did not have the same problem. |
@avh-on1 , thanks for your report. That's rather strange : did you notice any error message or any error entries in the log? |
Unfortunately the problem still exist:
I would recommend to add an information to http://wiki.yacy.net/index.php/En:DebianInstall until this problem is fixed. I'm very fascinated of the YaCy project but don't dare to recommend it if the official Debian installation does not work. Anway: Thx for YaCy! |
yacy_v1.92_20161226_9000.tar.gz "collapsed" on my Debian9 VM after a some monites so thank you very very for providing an alternative Debian package! One problem: Using yacy_v1.92_20161226_9000.tar.gz I could "import" my Lets Encrypt certificates as described by @Scarfmonster in #194 (comment) but with you package
while https://my.lan.server.ip:8443/ works with the self-signed certificate created by YaCy. So instead of pointing to |
@r4dh4l if you set the entry To conclude what you probably have to do, is to modify the entry with something like |
Thank you very much @luccioman.
and setting But may I ask anyway:
|
@r4dh4l you can name your custom Java keystore as you wish, I suggested About the |
FWIW I followed the debian install instructions under Kubuntu and it fails on the repos not being signed (
I attempted install with these slightly modified lines from the Debian instructions (to account for using sudo):
and also tried with
But, having seen that there's apparently been no working deb for 2 years whilst it's being advertised on the install page ... maybe I'm misreading but it doesn't seem like it's worth trying unless I want to get involved in modifying packages and troubleshooting permissions. As a "oh, that looks interesting" driveby from HackerNews, that's a big turn off. [That's not to say that anyone needs to fix anything, just to try and present how the project might appear to potential users.] |
Three years and:
Is there any chance this gets fixed someday or should I create a wiki account and put a big warning over all the articles referring to the package? |
I am considering this debian package as deprecated. I am also not able to fix this because I am not that familiar with debian certification processes. I would welcome if someone in the community wants to make a debian package and maintaines that package. I am also happy to link such work. Please help! |
I'm not going to use Docker. Does it even make sense to open issues for bugs I encounter when running from the tarball? |
ok |
After following the Debian repository setup instructions which succeeded with
sudo apt-get update
fails due toFurthermore accessing the repository through HTTPS in a browser fails because the certificate is untrusted. Trusted certificates are free to obtain and easy to maintain from initiatives like letsencrypt.org and state-of-the-art.
The text was updated successfully, but these errors were encountered: