Project

General

Profile

Bug #2613

[yacy] Signature no longer trusted.

ryry - about 4 years ago - . Updated about 4 years ago.

Status:
fixed
Priority:
bug
Assignee:
freemor
% Done:

100%

Description

Hi

On trying to install Yacy, I get the following, which is not fixed by the usual, Sudo pacman-key --refresh-keys

error: yacy: signature from "Luke R. <>" is unknown trust
:: File /var/cache/pacman/pkg/yacy-1.92-2-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

Just wondered if its an issue with an old signature etc? Or wether I have missed something.

Many thanks
ryry

Subtasks

Bug #2607: [yacy]: Option flag error on systemctl startfixedfreemor

Actions

History

#1

Updated by freemor about 4 years ago

Tried a quick rebuild of this to move it to my key as g4jc has not been around in forever.
PKGBUILD is VERY old circa 2016. Pulls a similarly old Version of YACY.

built OK with minor mods to the PKGBUILD but Failed to run with:

Jan 27 08:24:32 freelap systemd[1]: Started YaCy P2P Web Search.
Jan 27 08:24:32 freelap yacy[461879]: Starting YaCy Daemon
Jan 27 08:24:32 freelap yacy[461888]: OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
Jan 27 08:24:32 freelap yacy[461888]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
Jan 27 08:24:32 freelap yacy[461888]: Unrecognized VM option 'CMSIncrementalMode'
Jan 27 08:24:32 freelap yacy[461888]: Error: Could not create the Java Virtual Machine.
Jan 27 08:24:32 freelap yacy[461888]: Error: A fatal exception has occurred. Program will exit.
Jan 27 08:24:32 freelap systemd[1]: yacy.service: Main process exited, code=exited, status=1/FAILURE
Jan 27 08:24:32 freelap systemd[1]: yacy.service: Failed with result 'exit-code'.

Clearly the version of YACY this is trying to build is so old modern Java is alergic to it.

Will take a look and see if there is a newer version of YACY to pull. If not this may be one for the dust bin.

#2

Updated by freemor about 4 years ago

  • % Done changed from 0 to 10
  • Assignee set to freemor
  • Status changed from unconfirmed to in progress

There is a newer tarball. tried using it.
Built but failed to start with same errors.

Reading the YACY docs it needs java 8. problem is that ant (usid to compile it) Requires java-environment
which requirea java 13
So when I try to focre java 8 if breaks java-environment which break ant which means the buid() section is fubar'd

The YACY install instructions recommend running a script in the tarball to build/install it I'll take a look at that and see if something can be done

#3

Updated by bill-auger about 4 years ago

presuming that 'ant' is the only blocker, maybe that can be re-build with the PKGBUILD deps fixed to java-environment=8 - or maybe an 'ant' package can be installed from the archive

#4

Updated by bill-auger about 4 years ago

  • Parent task set to #2405
#5

Updated by freemor about 4 years ago

A subtilty that I haven't had to use before, thanks for pointing it out.
java-environment=8 does indeed get it to build. Still fails in the face
more then one Java environment. So I'll need to tweak it to start with Java 8
just in case people already have Java current in and then install Yacy which
pulls java 8 in beside java current.

#6

Updated by freemor about 4 years ago

  • Parent task deleted (#2405)

Rebuild on my key fand pushed fixes this issue.
now depends and is forced to use jdk8 shoud fix #2607 (runs for me even in the face of mixed Java Versions)

Closing both

#7

Updated by freemor about 4 years ago

  • Status changed from in progress to fixed

Also available in: Atom PDF