Package Details: yed 3.17.2-1

Git Clone URL: (read-only)
Package Base: yed
Description: Very powerful graph editor written in java
Upstream URL:
Licenses: custom
Submitter: fatmike
Maintainer: Bevan
Last Packager: Bevan
Votes: 222
Popularity: 1.101368
First Submitted: 2009-03-08 11:56
Last Updated: 2017-11-25 19:02

Latest Comments

Bevan commented on 2017-11-25 19:43

Ah, that may have been related to the new version that was available and is now reflected in this package.

andreab82 commented on 2017-11-25 19:40

Ok, my comment on "validpgpkeys" was wrong, investigating further it looks like it was an issue with sha256sums.

I installed archlinux-java-run separately with no problems.
Then on "makepkg -sri" I got:
"==> Validating source files with sha256sums... ... FAILED
yed.desktop ... Passed
yed ... Passed
==> ERROR: One or more files did not pass the validity check!"

Just now though, it installed correctly!
So definitely not a problem with your package, just not sure why it failed earlier.. weird.

Thanks for the quick response!

Bevan commented on 2017-11-25 19:05

andreab82: validpgpkeys would require yWorks to provide signatures for their files. Do you have an issue with building this package? It should be as simple as running "makepkg" after making sure that all dependencies are installed.

andreab82 commented on 2017-11-25 03:39

Hi, would it be possible to add the validpgpkeys please?
Otherwise any suggestion on how to build the package would be appreciated.

Bevan commented on 2017-11-17 22:33

rainbyte: Thanks for the hint! Does yEd work well for you using Java 9?

I'll try to come up with a more general version of the start script over the weekend. Your change looks good but if anymore still has jdk7 set as default it will still break because the java executable has moved in jdk9.

rainbyte commented on 2017-11-17 07:19

This error appears when using jre9-openjdk to run yed:

/usr/bin/yed: line 8: /usr/lib/jvm/java-9-openjdk/jre/bin/java: No such file or directory

To make it work with this jre, I have changed the conditional on /usr/bin/yed to this one:

if [[ "$(archlinux-java get)" =~ ^java-(8|9)-* ]]; then

Bevan commented on 2017-08-31 13:35

simon_sjw: I updated the package to fix the issue with the checksum. To your openssl issue: You should try to figure out why the openssl.cnf in some pacaur cache dir is chosen by default. This doesn't look like a healthy setup…

simon_sjw commented on 2017-08-31 11:57

Thanks Bevan,
I tried using git clone and then makepkg -si and still got the same error.

Looking at the forums, it turns out that locating my openssl.cnf file and exporting my $OPENSSL_CONF env. variable helps:

export OPENSSL_CONF=/etc/ssl/openssl.cnf

but it's now failing on checking the sha256sums.
I can see a few options included on the mail from ardemiranda below but when I try replacing the sha256sums line in PKGBUILD with the one on the bottom (since I'm >3.16) I get no joy.

Any thoughts?



Bevan commented on 2017-08-30 06:44

simon_sjw: This seems to be unrelated to this package but rather an issue with pacaur. You should be able to build this package manually as described in the wiki:

simon_sjw commented on 2017-08-30 01:52

Currently have the below error on installation.
UPDATE -> appears related to the issues commented below.
I lack the skills to apply the new sha256sum hash although would be keen to give it a crack if someone can point me in the right direction.

Message on install using pacaur -S yed on zsh:

:: Checking yed integrity...
==> Making package: yed 3.17-1 (Wed Aug 30 11:49:03 AEST 2017)
==> Retrieving sources...
-> Found
-> Found yed.desktop
-> Found yed
==> Validating source files with sha256sums... ... WARNING: can't open config file: /home/simon/.cache/pacaur/anaconda/pkg/anaconda/opt/anaconda/ssl/openssl.cnf
yed.desktop ... WARNING: can't open config file: /home/simon/.cache/pacaur/anaconda/pkg/anaconda/opt/anaconda/ssl/openssl.cnf
yed ... WARNING: can't open config file: /home/simon/.cache/pacaur/anaconda/pkg/anaconda/opt/anaconda/ssl/openssl.cnf
==> ERROR: One or more files did not pass the validity check!
:: failed to verify yed integrity

All comments